From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: Mark Kettenis <kettenis@chello.nl>,
GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Moving x86-64 configuration to separate directory
Date: Tue, 28 May 2002 09:23:00 -0000 [thread overview]
Message-ID: <20020528091745.J22765@dr-evil.shagadelic.org> (raw)
In-Reply-To: <3CF374D0.1030709@suse.cz>; from mludvig@suse.cz on Tue, May 28, 2002 at 02:15:12PM +0200
On Tue, May 28, 2002 at 02:15:12PM +0200, Michal Ludvig wrote:
> I was told it isn't possible to have gdb supporting both x86-64 and i386
> unless i386 is fully mutliarched. And after it is I don't need to treat
> them as different flavors of one arch, do I?
But further decoupling the x86-64 code from the i386 code isn't going
to make it easier to remedy the situation in the future.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-05-28 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 15:41 Mark Kettenis
2002-05-28 1:11 ` Jason R Thorpe
2002-05-28 7:29 ` Michal Ludvig
2002-05-28 9:23 ` Jason R Thorpe [this message]
-- 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=20020528091745.J22765@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--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