From: Michal Ludvig <mludvig@suse.cz>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Crossdebugging compilation fix for x86-64
Date: Mon, 04 Mar 2002 10:08:00 -0000 [thread overview]
Message-ID: <3C83B7FC.9030803@suse.cz> (raw)
In-Reply-To: <jepu2kgqhw.fsf@sykes.suse.de>
Andreas Schwab wrote:
> 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).
I already did this change in my tree and will post a patch for approval
tomorrow.
And what about these declarations:
gdbarch_frame_saved_pc_ftype x86_64_linux_frame_saved_pc;
gdbarch_saved_pc_after_call_ftype x86_64_linux_saved_pc_after_call;
Shouldn't they go away from the header as well, so that only #defines
will remain there as on other architectures?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
next prev parent reply other threads:[~2002-03-04 18:08 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
2002-03-04 10:08 ` Michal Ludvig [this message]
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=3C83B7FC.9030803@suse.cz \
--to=mludvig@suse.cz \
--cc=gdb-patches@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