From: Andreas Jaeger <aj@suse.de>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: x86_64 file names?
Date: Mon, 13 Aug 2001 23:46:00 -0000 [thread overview]
Message-ID: <ho3d6vb0l2.fsf@gee.suse.de> (raw)
In-Reply-To: <3B787018.5040700@cygnus.com>
Andrew Cagney <ac131313@cygnus.com> writes:
> In looking through the BFD sources I came:
>
> * bfd/elf64-x86-64.c
> gas/testsuite/gas/i386/x86_64.d
> gas/testsuite/gas/i386/x86_64.s
> * include/elf/x86-64.h
> ld/emulparams/elf_x86_64.sh
>
> this prompted me to wonder. Should the gdb file be called
> x86_64-tdep.c or x86-64-tdep.c. I really don't care but suspect the
> latter is more consistent with the core binutils files.
>
> So a question for the SuSE folks, what are the core GCC files being called?
The architecture is called x86-64. Since config.guess/config.sub will
not accept a minus, we had to use x86_64 for config.guess and that's
how this crept in. So in general, the name should be x86-64.
For GCC all the patches are done to the i386 files and there's no
x86-64 file at all.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
prev parent reply other threads:[~2001-08-13 23:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 17:26 Andrew Cagney
2001-08-13 23:46 ` Andreas Jaeger [this message]
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=ho3d6vb0l2.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
/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