From: Andreas Schwab <schwab@suse.de>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Crossdebugging compilation fix for x86-64
Date: Mon, 04 Mar 2002 10:03:00 -0000 [thread overview]
Message-ID: <jepu2kgqhw.fsf@sykes.suse.de> (raw)
In-Reply-To: <20020304112017.A19528@nevyn.them.org> (Daniel Jacobowitz's message of "Mon, 4 Mar 2002 11:20:17 -0500")
Daniel Jacobowitz <drow@mvista.com> writes:
|> On Mon, Mar 04, 2002 at 01:29:58PM +0100, Michal Ludvig wrote:
|> > Index: ChangeLog
|> > from Michal Ludvig <mludvig@suse.cz>
|> >
|> > * MAINTAINERS (x86-64): Target is not broken anymore.
|> > * x86-64-tdep.h (sys/reg.h): Delete
|> > (R15, R14, R13, R12, RBP, RBX, R11, R10, R9, R8, RAX, RCX, RDX,
|> > RSI, RDI, ORIG, RIP, CS, EFLAGS, RSP, SS): Define. These can't be
|> > included from sys/reg.h when compiling for cross-debuging.
|>
|> These belong in a Linux-specific file. Their order is not dependent on
|> anything in the x86-64 ABI, is it?
What puzzles me more is the fact that x86_64_regmap is defined (and not
just declared) in a header. It is only used in x86-64-linux-nat.c, so it
should be moved there (and that file can use <sys/reg.h> freely).
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-03-04 18:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-04 4:30 Michal Ludvig
2002-03-04 8:20 ` Daniel Jacobowitz
2002-03-04 10:03 ` Andreas Schwab [this message]
2002-03-04 10:08 ` Michal Ludvig
2002-03-04 12:24 ` 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=jepu2kgqhw.fsf@sykes.suse.de \
--to=schwab@suse.de \
--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