Re: [gentoo-user] Which -march and flags for Intel Dual Core (*NOT* Core Duo)?

2007-09-01 Thread Walter Dnes
On Wed, Aug 29, 2007 at 09:43:35PM -0400, Statux wrote

 CFLAGS=-march=prescott -O2 -pipe
 CHOST=i686-pc-linux-gnu
 
 which is what I use on my 531 Prescott (the pni cpuflag indicates
 Prescott or compatible)

  Thanks.  I don't know if I'm reading the gcc docs too literally, but
the commentary on -mfpmath=sse indicates that mmx/sse/sse/sse3 flags
must be explicitly stated for -mfpmath=sse to take effect on a 32-bit
system (sse is the default on 64-bit systems).  So I explicitly included
the flags.  I also included -fomit-frame-pointer, resulting in...

CFLAGS=-O2 -march=prescott -mmmx -msse -msse2 -msse3 -mfpmath=sse 
-fomit-frame-pointer -pipe

-- 
Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1
Q. Mr. Ghandi, what do you think of Microsoft security?
A. I think it would be a good idea.
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Which -march and flags for Intel Dual Core (*NOT* Core Duo)?

2007-09-01 Thread Volker Armin Hemmann
On Samstag, 1. September 2007, Walter Dnes wrote:
 On Wed, Aug 29, 2007 at 09:43:35PM -0400, Statux wrote

  CFLAGS=-march=prescott -O2 -pipe
  CHOST=i686-pc-linux-gnu
 
  which is what I use on my 531 Prescott (the pni cpuflag indicates
  Prescott or compatible)

   Thanks.  I don't know if I'm reading the gcc docs too literally, but
 the commentary on -mfpmath=sse indicates that mmx/sse/sse/sse3 flags
 must be explicitly stated for -mfpmath=sse to take effect on a 32-bit
 system (sse is the default on 64-bit systems).  So I explicitly included
 the flags.  I also included -fomit-frame-pointer, resulting in...

 CFLAGS=-O2 -march=prescott -mmmx -msse -msse2 -msse3 -mfpmath=sse
 -fomit-frame-pointer -pipe

mmx, sse,sse2,sse3 is already set by prescott (if man gcc can be trusted but 
it should not hurt to set them) but mfpmath can result in subtile breakage. 
fomit-frame-pointer is ok, O2 too.

 CFLAGS=-O2 -march=prescott -fomit-frame-pointer -pipe is much safer.



-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Which -march and flags for Intel Dual Core (*NOT* Core Duo)?

2007-08-30 Thread Michal 'vorner' Vaner
Hello

On Wed, Aug 29, 2007 at 09:14:06PM -0400, Walter Dnes wrote:
   Two identical cores show up in /proc/cpuinfo.  To save space on the
 list, I'm only listing the 2nd one.  I'm about to do an install.  Any
 ideas for USE and other settings also welcome.

gcc 4.something (I hope it is already on the live CDs) have a cute
feature. --march=native, and it will look at the CPU and decide itself
what best it can do about it.

-- 
~, sweet ~

Michal 'vorner' Vaner


pgp9i2BETu8uS.pgp
Description: PGP signature


Re: [gentoo-user] Which -march and flags for Intel Dual Core (*NOT* Core Duo)?

2007-08-30 Thread Florian Philipp
Am Donnerstag 30 August 2007 03:43:35 schrieb Statux:
 On Wed, 2007-08-29 at 21:14 -0400, Walter Dnes wrote:
  Two identical cores show up in /proc/cpuinfo.  To save space on the
  list, I'm only listing the 2nd one.  I'm about to do an install.  Any
  ideas for USE and other settings also welcome.
 
  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 15
  model name  : Genuine Intel(R) CPU2140  @ 1.60GHz
  stepping: 2
  cpu MHz : 1596.041
  cache size  : 1024 KB
  physical id : 0
  siblings: 2
  core id : 1
  cpu cores   : 2
  fdiv_bug: no
  hlt_bug : no
  f00f_bug: no
  coma_bug: no
  fpu : yes
  fpu_exception   : yes
  cpuid level : 10
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
  mca cmov
  pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm
  constant_tsc pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
  bogomips: 3192.10

 If it's going to be a 32bit system, then personally, I would use:

 CFLAGS=-march=prescott -O2 -pipe
 CHOST=i686-pc-linux-gnu

 which is what I use on my 531 Prescott (the pni cpuflag indicates
 Prescott or compatible)

 If you are doing a 64bit system, then use -march=nocona and
 CHOST=x86_64-pc-linux-gnu and remember to use a 64bit livecd for the
 install like the one for amd64 unless they've got something better now
 adays.

 That's my $0.02. Anyone else have additions/corrections? :-)


I suppose Walter meant Which -march and flags for Intel Core Duo (*NOT* Core 
2 Duo)

In that case the first settings you've posted are correct.


signature.asc
Description: This is a digitally signed message part.


[gentoo-user] Which -march and flags for Intel Dual Core (*NOT* Core Duo)?

2007-08-29 Thread Walter Dnes
  Two identical cores show up in /proc/cpuinfo.  To save space on the
list, I'm only listing the 2nd one.  I'm about to do an install.  Any
ideas for USE and other settings also welcome.

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 15
model name  : Genuine Intel(R) CPU2140  @ 1.60GHz
stepping: 2
cpu MHz : 1596.041
cache size  : 1024 KB
physical id : 0
siblings: 2
core id : 1
cpu cores   : 2
fdiv_bug: no
hlt_bug : no
f00f_bug: no
coma_bug: no
fpu : yes
fpu_exception   : yes
cpuid level : 10
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
bogomips: 3192.10


-- 
Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1
Q. Mr. Ghandi, what do you think of Microsoft security?
A. I think it would be a good idea.
-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-user] Which -march and flags for Intel Dual Core (*NOT* Core Duo)?

2007-08-29 Thread Statux
On Wed, 2007-08-29 at 21:14 -0400, Walter Dnes wrote:
 Two identical cores show up in /proc/cpuinfo.  To save space on the
 list, I'm only listing the 2nd one.  I'm about to do an install.  Any
 ideas for USE and other settings also welcome.
 
 processor : 1
 vendor_id : GenuineIntel
 cpu family: 6
 model : 15
 model name: Genuine Intel(R) CPU2140  @ 1.60GHz
 stepping  : 2
 cpu MHz   : 1596.041
 cache size: 1024 KB
 physical id   : 0
 siblings  : 2
 core id   : 1
 cpu cores : 2
 fdiv_bug  : no
 hlt_bug   : no
 f00f_bug  : no
 coma_bug  : no
 fpu   : yes
 fpu_exception : yes
 cpuid level   : 10
 wp: yes
 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
 pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc 
 pni monitor ds_cpl est tm2 ssse3 cx16 xtpr lahf_lm
 bogomips  : 3192.10
 

If it's going to be a 32bit system, then personally, I would use:

CFLAGS=-march=prescott -O2 -pipe
CHOST=i686-pc-linux-gnu

which is what I use on my 531 Prescott (the pni cpuflag indicates
Prescott or compatible)

If you are doing a 64bit system, then use -march=nocona and
CHOST=x86_64-pc-linux-gnu and remember to use a 64bit livecd for the
install like the one for amd64 unless they've got something better now
adays.

That's my $0.02. Anyone else have additions/corrections? :-)

 
 -- 
 Walter Dnes [EMAIL PROTECTED] In linux /sbin/init is Job #1
 Q. Mr. Ghandi, what do you think of Microsoft security?
 A. I think it would be a good idea.
-- 
Statux [EMAIL PROTECTED]


signature.asc
Description: This is a digitally signed message part