I have only amd-based systems (pc's anyway) at home, and have only one p3/p4-based system at the office, but I have not had any problems using the "intel" versions of OOo.

I must admit that I missed the original post (and can't find it in my archives where I save everything), but if the writer's point was something like "don't amd's have features supported by gcc which are not present in the p3/p4 version" then I can understand this one, because in *some* (but by no means all) cases it is possible to speed up som eprogram executions by compiling for that architecture.

Before I switched to the fedora releases at home, I would routinely rebuild glibc and some other necessary rpms in order to be able to take advantage of (for instance) the faster number crunching and some of the string handling functions which the athlon had but the intel did not. Of course, I had to write my own assembler routines and add them to glibc, too, so this is *not* a trick for the faint-hearted. But these days, I'v gotten lazier and haven't done that since the "athlon" kernel stopped building in the kernel-xyx.src.rpm releases. (BTW, the best case except for number crunching came up with only a small improvement, 1-4% speed increase if memory serves ...)

So yes, it might work faster to create an athlon version, but you might also have to update/replace system libraries and kernel. And such is NOT a trival activity :-)

- william

On 2005-08-07 14:45:47, CPHennessy wrote:
On Sunday 07 August 2005 13:08, + J. Greenlees wrote:
>  [ MODERATED ] ***********************
> why is it default to intel?
> since hp ( amongst other manufacturers ) has for years been
standardised
> with amd, there is an equal number of win32 systems that would get a
more
> stable working environment with an amd specific build.
>
> noticed the intel in the version name when downloading the 1.9.x
beta just
> now.

Hi Jaqui,
 You will find that any OOo package with the name "intel" in it should
work
perfectly on AMD cpus. If they do not, then there is a bug and it
should be
reported.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to