Differences between current version and revision by previous author of amd64.
Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History
| Newer page: | version 7 | Last edited on Tuesday, February 1, 2005 1:10:21 am | by AristotlePagaltzis | |
| Older page: | version 6 | Last edited on Monday, January 31, 2005 4:00:18 pm | by CraigBox | Revert |
@@ -1,16 +1,14 @@
-[AMD]'s [64bit] architecture, used in their Opteron and Athlon64 [CPU]s. Also
known as __x86-64__. They are
[AMD]'s attempt to compete with [Intel]'s [ia64] and gain a foothold
in the server market. Read [more at amd.com | http
://www.amd.com/us-en/Processors/ProductInformation/,,30_118_9331,00.html]
+[AMD]'s [64bit] architecture, used in their Opteron and Athlon64 [CPU]s, and also
known as __x86-64__. It is the first major evolution of the [x86] platform since the i386 and has been adopted by [Intel] under the name [EM64T]. The Opteron line is
[AMD]'s attempt to compete with [Intel] in the server market. Some things to beware of
:
-This promises to be a major revolution in archetecture of the 80x86 line of processors, such that we've not seen since the 8086 to the 80286 and the 80286 to the 80386
.
+!! Use [GCC] 3
.4 and above!
------
-Some things to beware of:
-!!use gcc3.4 and above!
-gcc3
.3 and below cannot generate correct code for the
amd64.
If you have mysterious problems with programs crashing unexpectantly in what is normal code, then it's almost certain that you are not using a recent enough compiler. mozilla
shows this problem and will crash on startup.
+[GCC] 3
.3 and below cannot generate correct code for [
amd64]
. If you have mysterious problems with programs crashing unexpectantly in what is normal code, then it's almost certain that you are not using a recent enough compiler. [Mozilla]
shows this problem and will crash on startup.
-This poses a problem as a lot of programs won't compile with the newer gcc3
.4 compiler, as they voilate some rules of the C specification that gcc3
.4 now enforces where earlier compilers didn't.
This problem should disappear with time, but if it is a pain when it does surface.
I have personally solved this issue in the past by using the gcc2
.96 cpp to preprocess code, and the gcc3
.4 executable
to generate the actual executable.
Other hand hacking may be required.
+This poses a problem as a lot of programs won't compile with the newer [GCC] 3
.4 compiler, as they voilate some rules of the [
C]
specification that [GCC] 3
.4 now enforces where earlier compilers didn't. This problem should disappear with time, but if it is a pain when it does surface. I have personally solved this issue in the past by using the [GCC] 2
.96 <tt>
cpp</tt>
to preprocess code, and [GCC] 3
.4 to generate the actual executable. Other hand hacking may be required.
-!!Some code isn't 64bit clean.
-It's difficult to write portable code in C that deals properly with archetectures of difference
sizes.
For instance using a uint64_t to make sure a type is 64bits long, then trying to printf it causes problems.
See [CPortabilityNotes].
+!! Some code isn't 64bit clean
+
+It's difficult to write portable code in [
C]
that deals properly with architectures with different word
sizes. For instance using a <tt>
uint64_t</tt>
to make sure a type is 64bits long, then trying to printf(3)
it causes problems. See [CPortabilityNotes].
----
CategoryProgramming, CategoryHardware
