Re: __AMD64__ or __amd64__ ?
MH If the test is just to determine wether or not a 64bit MH architecture is being built for, then __arch64__ is a better MH test. What is a 64 bit architecture? Is it about address bus size? (The MC68020 is a 34-bit architecture?) About data bus size? About register size? (The MC68040 is an 80-bit architecture?) About the size that instructions operate on? (The P6 is a 128-bit architecture?) LP64 has a well-defined technical meaning (it's about the size of data types exported by the C compiler.) I have no idea what ``64-bit architecture'' may mean. Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: __AMD64__ or __amd64__ ?
On Thu, 4 Mar 2004, Juliusz Chroboczek wrote: MH If the test is just to determine wether or not a 64bit MH architecture is being built for, then __arch64__ is a better MH test. What is a 64 bit architecture? Is it about address bus size? (The MC68020 is a 34-bit architecture?) About data bus size? About register size? (The MC68040 is an 80-bit architecture?) About the size that instructions operate on? (The P6 is a 128-bit architecture?) LP64 has a well-defined technical meaning (it's about the size of data types exported by the C compiler.) I have no idea what ``64-bit architecture'' may mean. There is really no need to be a troll when someone is trying to provide useful helpful advice. If you do not know what __arch64__ is, then by all means read ISO C99 and/or the gcc or other documentation. This mailing list is getting more sickening and useless every day with useless commentary like yours in response to a helpful message. I guess when the ship sinks however, the whole thing goes down, not just part of it. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: __AMD64__ or __amd64__ ?
Matthieu Herrb writes: Hi, While working on OpenBSD/amd64 support for XFree86, I found out that the C preprocessor symbol for AMD64 machines was changed from __x86_64__ to __AMD64__. But looking at what gcc defines on different AMD63 systems (*BSD, Linux), it looks __AMD64__ is never used. Generally __amd64__ is defined. linux.cf add -D__AMD64__ to StandardCppDefines, so the code actually works there. Also, in many places where checks are done for 64 bits arches, the test is in the form #if defined(_LP64) || defined(__alpha__) || defined(__AMD64__). Since on the BSDs gcc defines _LP64, these conditions will be true. But there are a few cases where the _LP64 test is missing. LP64 should be set correctly by more recent versions of gcc and should be used instead of the architectural defines for identifying wether long is 32 or 64 bit. I would think that any versions of gcc for AMD64 which were ever released to the wild seem to set this correctly. Any clues on how to fix that correctly (after 4.4) ? Instead of enumerating all the LP64 arches in several different places, it would be better imho to make sure _LP64 is defined and only testing on this. For other cases (where the dependance is not a general LP64 problem, but AMD64 specific, it would be more logic imho to use __amd64__. Right. It should be straight forward to change this. I used a script to change it fron __x86_64__ to __AMD64__ when AMD announced this name. (That was what I was told to use if I remember correctly). However everything should work as long as the define __x86_64__ is still supported by gcc. Egbert. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
__AMD64__ or __amd64__ ?
Hi, While working on OpenBSD/amd64 support for XFree86, I found out that the C preprocessor symbol for AMD64 machines was changed from __x86_64__ to __AMD64__. But looking at what gcc defines on different AMD63 systems (*BSD, Linux), it looks __AMD64__ is never used. Generally __amd64__ is defined. linux.cf add -D__AMD64__ to StandardCppDefines, so the code actually works there. Also, in many places where checks are done for 64 bits arches, the test is in the form #if defined(_LP64) || defined(__alpha__) || defined(__AMD64__). Since on the BSDs gcc defines _LP64, these conditions will be true. But there are a few cases where the _LP64 test is missing. Any clues on how to fix that correctly (after 4.4) ? Instead of enumerating all the LP64 arches in several different places, it would be better imho to make sure _LP64 is defined and only testing on this. For other cases (where the dependance is not a general LP64 problem, but AMD64 specific, it would be more logic imho to use __amd64__. Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: __AMD64__ or __amd64__ ?
Matthieu Herrb wrote: Also, in many places where checks are done for 64 bits arches, the test is in the form #if defined(_LP64) || defined(__alpha__) || defined(__AMD64__). Since on the BSDs gcc defines _LP64, these conditions will be true. But there are a few cases where the _LP64 test is missing. A number of the _LP64's were added just recently (bugzilla #477). It's also the correct flag for use on Solaris, both for 64-bit on SPARC and the upcoming AMD-64 port. -- -Alan Coopersmith- [EMAIL PROTECTED] Sun Microsystems, Inc. -- Operating Platforms Group Solaris x86 Interface Technology: X Window System ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: __AMD64__ or __amd64__ ?
On Sat, 28 Feb 2004, Matthieu Herrb wrote: While working on OpenBSD/amd64 support for XFree86, I found out that the C preprocessor symbol for AMD64 machines was changed from __x86_64__ to __AMD64__. But looking at what gcc defines on different AMD63 systems (*BSD, Linux), it looks __AMD64__ is never used. Generally __amd64__ is defined. linux.cf add -D__AMD64__ to StandardCppDefines, so the code actually works there. Also, in many places where checks are done for 64 bits arches, the test is in the form #if defined(_LP64) || defined(__alpha__) || defined(__AMD64__). Since on the BSDs gcc defines _LP64, these conditions will be true. But there are a few cases where the _LP64 test is missing. Any clues on how to fix that correctly (after 4.4) ? Instead of enumerating all the LP64 arches in several different places, it would be better imho to make sure _LP64 is defined and only testing on this. If the test is just to determine wether or not a 64bit architecture is being built for, then __arch64__ is a better test. I've noticed a bunch of places in the source which test for each possible 64bit architecture, and which need to have any new 64bit arches added as time goes on. __arch64__ would fix that also. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
