In <[EMAIL PROTECTED]>, Zavam, Vinícius <[EMAIL PROTECTED]> typed:
> 2007/6/26, Garrett Cooper <[EMAIL PROTECTED]>:
> > Mike Meyer wrote:
> > nowadays).
> > >> Intel suggests using -march=prescott (32-bit) and -march=nocona
> > >> (64-bit) with gcc on Core2Duo processors and equivalent Xeons.
>
2007/6/26, Garrett Cooper <[EMAIL PROTECTED]>:
Mike Meyer wrote:
> In <[EMAIL PROTECTED]>, Garrett Cooper <[EMAIL PROTECTED]> typed:
>
>> Martin Turgeon wrote:
>>
>>> Mike Meyer a écrit :
>>>
In <[EMAIL PROTECTED]>, Roman Divacky
<[EMAIL PROTECTED]> typed:
For the record, I believe
Mike Meyer wrote:
In <[EMAIL PROTECTED]>, Garrett Cooper <[EMAIL PROTECTED]> typed:
Martin Turgeon wrote:
Mike Meyer a écrit :
In <[EMAIL PROTECTED]>, Roman Divacky
<[EMAIL PROTECTED]> typed:
For the record, I believe the nocona cores are:
pentium 4/some prescott, prescott 2m,
In <[EMAIL PROTECTED]>, Garrett Cooper <[EMAIL PROTECTED]> typed:
> Martin Turgeon wrote:
> > Mike Meyer a écrit :
> >> In <[EMAIL PROTECTED]>, Roman Divacky
> >> <[EMAIL PROTECTED]> typed:
> >> For the record, I believe the nocona cores are:
> >> pentium 4/some prescott, prescott 2m, cedar mill
>
Martin Turgeon wrote:
Mike Meyer a écrit :
In <[EMAIL PROTECTED]>, Roman Divacky
<[EMAIL PROTECTED]> typed:
you should know what cpu you bought, or just use cpuid (found in ports)
and determine what cpu you have.
Knowing what CPU you bought doesn't help a lot for the case asked
about o
Mike Meyer a écrit :
In <[EMAIL PROTECTED]>, Roman Divacky <[EMAIL PROTECTED]> typed:
you should know what cpu you bought, or just use cpuid (found in ports)
and determine what cpu you have.
Knowing what CPU you bought doesn't help a lot for the case asked
about of "nocona" vs. "presco
In <[EMAIL PROTECTED]>, Roman Divacky <[EMAIL PROTECTED]> typed:
> you should know what cpu you bought, or just use cpuid (found in ports)
> and determine what cpu you have.
Knowing what CPU you bought doesn't help a lot for the case asked
about of "nocona" vs. "prescott". Those are the names of P
> In general, how does one decide which CPUTYPE to use? The connection
> between the options for CPUTYPE and the output of dmesg is not so
> obvious to me. I looked at the features advertised by dmesg (which in
> my case included SSE3) and then reverse engineered bsd.cpu.mk to figure
> out I
On Mon, Jun 25, 2007 at 12:45:37PM -0500, Stephen Montgomery-Smith wrote:
> Also, does setting CPUTYPE make a lot of difference to performance?
I don't notice any difference in performance on my Athlon xp 2400
box if I set CPUTYPE=athlon-xp vs. leaving it alone.
YMMV though, ask the gentoo peopl
Jack L. wrote:
On 6/24/07, Martin Turgeon <[EMAIL PROTECTED]> wrote:
Hi,
I recently installed AMD64 6.2 Release on 2 PowerEdge servers, both with
dual core Xeon (3070 and 5110). I noticed when I was updating the
sources that it was compiling as an Athlonxp by default. I was wondering
if I shoul
10 matches
Mail list logo
