Re: [gentoo-user] gcc 4.2 and Core 2 Duo

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kenneth Prugh wrote: > Vladimir G. Ivanovic wrote: > >> You, of course, remembered to change your default compiler with >> >># gcc-config -gnu-4.2.0 >> >> before recompiling everything. (Run 'gcc-config' with no arguments for >> more info.) >> >>

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Vladimir G. Ivanovic wrote: > You, of course, remembered to change your default compiler with > ># gcc-config -gnu-4.2.0 > > before recompiling everything. (Run 'gcc-config' with no arguments for > more info.) > > --- Vladimir Yep. I've also seen that with march/mtune set to native, GCC 4.

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kenneth Prugh wrote: > Andrew Gaydenko wrote: The question is: must I replace '-march=nocona' with '-mtune=native and -march=native'? >>> I have a Core2 Duo E6600 and use these CFLAGS with GCC 4.2: >>> >>> CFLAGS="-Os -march=native -mtune=na

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

On Freitag, 20. Juli 2007, Tobias Heinlein wrote: > Volker Armin Hemmann wrote: > > On Freitag, 20. Juli 2007, Andrew Gaydenko wrote: > > march and mtune together? stupid. > > mmmx, msse2, mss3 stupid. Its all part of nocona (maybe not msse3 but > > everything else). > > Yes, that's right. These fl

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Volker Armin Hemmann wrote: > On Freitag, 20. Juli 2007, Andrew Gaydenko wrote: > march and mtune together? stupid. > mmmx, msse2, mss3 stupid. Its all part of nocona (maybe not msse3 but > everything else). Yes, that's right. These flags don't need to be set again. But there are some ebuilds th

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Kenneth Prugh wrote: > Andrew Gaydenko wrote: > The question is: must I replace '-march=nocona' with '-mtune=native and -march=native'? >>> I have a Core2 Duo E6600 and use these CFLAGS with GCC 4.2: >>> >>> CFLAGS="-Os -march=native -mtune=native -fomit-frame-pointer -p

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

On Friday 20 July 2007, "Boyd Stephen Smith Jr." <[EMAIL PROTECTED]> wrote about 'Re: [gentoo-user] gcc 4.2 and Core 2 Duo': > If they have the same value, or -march is listed after -mtune, yes. > -march implies -mtune, but you might do something like -march=686

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Andrew Gaydenko wrote: >>> The question is: must I replace '-march=nocona' with '-mtune=native and >>> -march=native'? >> I have a Core2 Duo E6600 and use these CFLAGS with GCC 4.2: >> >> CFLAGS="-Os -march=native -mtune=native -fomit-frame-pointer -pipe -mmmx >> -msse2 -msse3" >> >> Native works

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

> march and mtune together? stupid. > native when you know your CPU? Does your CHOST say 'x86_64' or nocona? > mmmx, msse2, mss3 stupid. Its all part of nocona (maybe not msse3 but > everything else). And fomit-frame-pointer? AFAIK superfluos on the amd64 > architecture, which was copied by intel

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Florian Philipp wrote: > Am Freitag 20 Juli 2007 20:16 schrieb Kenneth Prugh: >> Andrew Gaydenko wrote: >>> I have noticed, the official portage tree has included gcc 4.2. Now for >>> Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: >>> >>> CFLAGS="-O2 -march=nocona -pipe" >>> >>> gcc' c

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Volker Armin Hemmann wrote: > Second, that 'feature' means that gcc looks at your CHOST and use that for > the > march/mtune setting. > > So no, don't change anything at all. march=nocona is fine. Don't touch it. That's completely wrong. If you look at the old patch [1] that fixed mtune for the

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Am Freitag 20 Juli 2007 20:16 schrieb Kenneth Prugh: > Andrew Gaydenko wrote: > > I have noticed, the official portage tree has included gcc 4.2. Now for > > Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: > > > > CFLAGS="-O2 -march=nocona -pipe" > > > > gcc' changelog has this note: >

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

On Freitag, 20. Juli 2007, Andrew Gaydenko wrote: > I have noticed, the official portage tree has included gcc 4.2. Now for > Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: > > CFLAGS="-O2 -march=nocona -pipe" > > gcc' changelog has this note: > > > ... > IA-32/x86

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

> > > > The question is: must I replace '-march=nocona' with '-mtune=native and > > -march=native'? > > I have a Core2 Duo E6600 and use these CFLAGS with GCC 4.2: > > CFLAGS="-Os -march=native -mtune=native -fomit-frame-pointer -pipe -mmmx > -msse2 -msse3" > > Native works fine here. Kenneth

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Hello Andrew Gaydenko, > The question is: must I replace '-march=nocona' with '-mtune=native and > -march=native'? You CAN change them but there's no MUST about it. I've been running GCC 4.2 with -march=nocona for about ten days and it's working well. -- Neil Bothwick Linux like wigwam. No wi

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Andrew Gaydenko schrieb: > I have noticed, the official portage tree has included gcc 4.2. Now for > Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: > > CFLAGS="-O2 -march=nocona -pipe" > > gcc' changelog has this note: > > > ... > IA-32/x86-64 > > * -mtune

Re: [gentoo-user] gcc 4.2 and Core 2 Duo

Andrew Gaydenko wrote: > I have noticed, the official portage tree has included gcc 4.2. Now for > Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: > > CFLAGS="-O2 -march=nocona -pipe" > > gcc' changelog has this note: > > > ... > IA-32/x86-64 > > * -mtune=g

[gentoo-user] gcc 4.2 and Core 2 Duo

I have noticed, the official portage tree has included gcc 4.2. Now for Core 2 Duo CPU (amd64 Gentoo arch) I use in make.conf file: CFLAGS="-O2 -march=nocona -pipe" gcc' changelog has this note: ... IA-32/x86-64 * -mtune=generic can now be used to generate code running