Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: Mark Kettenis <kettenis@chello.nl>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Moving x86-64 configuration to separate directory
Date: Tue, 28 May 2002 07:29:00 -0000	[thread overview]
Message-ID: <3CF374D0.1030709@suse.cz> (raw)
In-Reply-To: <200205272200.g4RM0T400654@elgar.kettenis.dyndns.org>

Mark Kettenis wrote:
> Michal Ludvig <mludvig@suse.cz> writes:
>>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.

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?

 > In that case you should leave the files where they are now.
 > Incidentally that's what GCC does.

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* +420 2 9654 5373   * http://www.suse.cz


  parent reply	other threads:[~2002-05-28 12:15 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 [this message]
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=3CF374D0.1030709@suse.cz \
    --to=mludvig@suse.cz \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /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