From: Mark Kettenis <kettenis@chello.nl>
To: Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Moving x86-64 configuration to separate directory
Date: Mon, 27 May 2002 15:41:00 -0000 [thread overview]
Message-ID: <200205272200.g4RM0T400654@elgar.kettenis.dyndns.org> (raw)
In-Reply-To: Michal Ludvig's message of "Mon, 27 May 2002 16:52:58 +0200"
Michal Ludvig <mludvig@suse.cz> writes:
> Hi,
> I'm about to move all x86-64 configuration stuff to a separate
> directory. For now it resides in config/i386 but AFAIK this is a relict
> of cloning the the files from eachother, not the necessity.
> Yet more x86-64 is definitely a different architecture than i386 :-)
Is it really? My understanding is that it is comparable to sparc
vs. sparc64. Isn't it possiblle to execute normal 32-bit i386 code on
the x86_64? In that case, you'd probably want to have a GDB that can
handle both. The only way to be able to accomplish that in the near
future is seeing them as different variants of the same architecture.
In that case you should leave the files where they are now.
Incidentally that's what GCC does.
If you want these targets to become really seperate, we should
consider doing a repository copy of the files to preserve their
history.
Mark
next reply other threads:[~2002-05-27 22:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 15:41 Mark Kettenis [this message]
2002-05-28 1:11 ` Jason R Thorpe
2002-05-28 7:29 ` Michal Ludvig
2002-05-28 9:23 ` Jason R Thorpe
-- strict thread matches above, loose matches on Subject: below --
2002-05-27 8:05 Michal Ludvig
2002-05-27 11:10 ` Jason R Thorpe
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=200205272200.g4RM0T400654@elgar.kettenis.dyndns.org \
--to=kettenis@chello.nl \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@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