From: Jiri Smid <smid@suse.cz>
To: gdb@sources.redhat.com
Subject: Re: Port to x86-64
Date: Tue, 03 Apr 2001 01:42:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0104031041280.7569-100000@chimera.suse.cz> (raw)
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?
> >
> > I also wonder if you actually need a separate CVS repository and
> > couldn't just live on a branch of the official GDB repository? It
> > should make merging a lot easier.
>
> Working on a branch might be the better idea. Shall Jiri send his ssh
> key to you for setting this up? Jiri, what do you prefer?
>
I think that working on a branch is better too. Can I send ssh key? And
where?
--
Jiri Smid
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: smid@suse.cz
Drahobejlova 27 tel:+420 2 83095 373
190 00 Praha 9 fax:+420 2 83095 374
Ceska republika http://www.suse.cz
next reply other threads:[~2001-04-03 1:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 1:42 Jiri Smid [this message]
2001-04-06 12:23 ` Andrew Cagney
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 ` Andrew Cagney
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Andreas Jaeger
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=Pine.LNX.4.21.0104031041280.7569-100000@chimera.suse.cz \
--to=smid@suse.cz \
--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