From: Andreas Jaeger <aj@suse.de>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: Jiri Smid <smid@suse.cz>, gdb-patches@sources.redhat.com
Subject: Re: [RFA]: x86_64 target files
Date: Thu, 02 Aug 2001 09:37:00 -0000 [thread overview]
Message-ID: <u84rrqa0ap.fsf@gromit.moeb> (raw)
In-Reply-To: <Pine.SUN.3.91.1010802183244.3639C-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> On 2 Aug 2001, Jiri Smid wrote:
>
>> This is the related new files for x86-64 target.
Thanks!
> What is x86-64, exactly? Some of the files seem to hint that it's an AMD
> CPU, but others just say x86-64.
x86-64 is AMD's 64 bit architecture which is an 64-bit enhancement to
the ia32 (ix86) architecture. The step from 32-bit to 64-bit has been
done in a similar way as done by MIPS and SPARC for their CPUs.
In a nutshell:
x86-64 has 16 (instead of 8 for ia32) normal registers that hold
64-bit, 16 XMM (instead of 8 for ia32) registers used by SSE/SSE2 and
the x87 FPU.
For more details check http://www.x86-64.org - or ask me,
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-08-02 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 7:20 Jiri Smid
2001-08-02 8:39 ` Eli Zaretskii
2001-08-02 9:37 ` Andreas Jaeger [this message]
2001-08-02 9:43 ` Kevin Buettner
2001-08-09 22:53 ` Andrew Cagney
2001-08-09 23:12 ` config/i386/xm-x86_64.h; Was " Andrew Cagney
2001-08-09 23:25 ` configure.host; Was: " Andrew Cagney
2001-08-09 23:41 ` configure.tgt; " Andrew Cagney
2001-08-09 23:57 ` Misc; " Andrew Cagney
2001-08-30 1:35 ` Jiri Smid
2001-08-30 7:39 ` Andrew Cagney
2001-08-30 11:03 ` Andreas Jaeger
2001-08-30 16:53 ` Andrew Cagney
2001-08-31 0:13 ` Andreas Jaeger
2001-08-31 2:00 ` i386 flavors [Was: Re: Misc; Was: [RFA]: x86_64 target files] Andreas Jaeger
2001-08-31 10:39 ` Misc; Was: [RFA]: x86_64 target files Andrew Cagney
2001-08-31 13:12 ` Andreas Jaeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u84rrqa0ap.fsf@gromit.moeb \
--to=aj@suse.de \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=smid@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox