gcc -O flags (was GLIBC Coredump)

SamBC sambc at nights.force9.co.uk
Sun Jul 16 09:54:36 PDT 2000


"-mcpu= " seems an odd option


SamBC

> -----Original Message-----
> From: owner-lfs-discuss at pcrdallas.com
> [mailto:owner-lfs-discuss at pcrdallas.com]On Behalf Of Shawn Starr
> Sent: 16 July 2000 08:04
> To: Thomas T. Veldhouse
> Cc: lfs-discuss at linuxfromscratch.org
> Subject: Re: gcc -O flags (was GLIBC Coredump)
>
>
>
> hmm... glibc coredumped with -O2 -mcpu= -march=i586
> hehe i guess -O only works ;/
>
> On Sat, 15 Jul 2000, Thomas T. Veldhouse wrote:
>
> > I use -march=pentiumpro for everything.  I also use -O, but I don't mess
> > around with anything higher than -O.  I did get burned by it once using
> > gcc-2.95.2 and FreeBSD.  I think I was building the world and something
> > refused to work properly.  I don't really remember.
> >
> > Tom Veldhouse
> > veldy at veldy.net
> >
> > On Fri, 14 Jul 2000, Gerard Beekmans wrote:
> >
> > > > glibc seems to fail compiling with -O3 (I'm not ready with
> -O2 yet) but
> > > > how is it with other packages? Are there any more packages
> that will fail
> > > > to compile, or worse, compile but fail to work, when using
> -O2 or -O3 then
> > > > I would be glad to hear about it. Or should I just give up
> and use just -O
> > > > all the time?
> > >
> > > Personally I had no problems at all using -O3 and others like
> -mcpu and
> > > -march on Glibc and all the other packages. A few packages in the book
> > > don't use it because the hassle of editing the Makefile file
> is too big
> > > a hassle for what it's worth. But I did confirm that those packages do
> > > compile fine (on my machine that is)
> > >
> > > --
> > > Gerard Beekmans
> > > www.linuxfromscratch.org
> > >
> > > -*- If Linux doesn't have the solution, you have the wrong problem -*-
> > > --
> > > Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
> > > IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
> > > Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
> > > "unsubscribe" (without the quotation marks) in the body of the message
> > > (no subject is required)
> > >
> >
> > --
> > Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
> > IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
> > Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
> > "unsubscribe" (without the quotation marks) in the body of the message
> > (no subject is required)
> >
>
> --
> Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
> IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
> Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
> "unsubscribe" (without the quotation marks) in the body of the message
> (no subject is required)
>

--
Mail archive: http://www.pcrdallas.com/mail-archives/lfs-discuss
IRC access: server: irc.linuxfromscratch.org port: 6667 channel: #LFS
Unsubscribe: email lfs-discuss-request at linuxfromscratch.org and put
"unsubscribe" (without the quotation marks) in the body of the message
(no subject is required)



More information about the lfs-dev mailing list