From: Andrew Cagney <ac131313@cygnus.com>
To: Jiri Smid <smid@suse.cz>
Cc: gdb@sources.redhat.com
Subject: Re: Port to x86-64
Date: Fri, 06 Apr 2001 12:23:00 -0000 [thread overview]
Message-ID: <3ACE17BB.1D2BA022@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0104031041280.7569-100000@chimera.suse.cz>
Jiri Smid wrote:
>
> Hi,
>
> Andreas Jaeger <aj@suse.de> writes:
>
> > >
> > > o submit the configury mess early
> > >
> > > even if you don't have real code
> > > could I suggest thinking about
> > > separating this out so that
> > > you can get on with the real
> > > work.
> > >
>
> Before I will submit the configury mess I would like to little discuss
> about it.
> The generic name of CPU is x86_64 in already ported software. It seems
> that there shoud be create new config directory gdb/config/x86_64. But
> this processor is extended i386 architecture and many parts of code will
> be the same as in i386.
> I think that the best solution is to create this new config directory
> x86_64 and from tm-x86_64.h include i386/tm-i386.h and redefine some
> declarations. What do you think?
What convention, if any, was adopted by GCC and what do config.guess /
config.sub return?
I suspect that ``x86-64'' is going to be more acceptable than x86_64 a
file name.
Andrew
next prev parent reply other threads:[~2001-04-06 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 1:42 Jiri Smid
2001-04-06 12:23 ` Andrew Cagney [this message]
2001-04-06 15:02 ` Andreas Jaeger
-- strict thread matches above, loose matches on Subject: below --
2001-03-21 15:59 Jiri Smid
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Andreas Jaeger
2001-03-21 15:59 ` Andrew Cagney
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=3ACE17BB.1D2BA022@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@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