From: Randolph Chung <randolph@tausq.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sources.redhat.com, dave@hiauly1.hia.nrc.ca,
brobecker@adacore.com
Subject: Re: Register numbers on hppa64
Date: Sun, 27 Nov 2005 16:30:00 -0000 [thread overview]
Message-ID: <4389CC73.9060706@tausq.org> (raw)
In-Reply-To: <200511261719.jAQHJnTd015739@elgar.sibelius.xs4all.nl>
> If fixing things for GCC means that we break the HP compilers, we
> should do so: GDB is part of the GNU project so its primary job should
> be supporting the GNU compiler, not some proprietary compiler.
While I do not disagree either from a pragmatic (ability to test) and a
philosophical point of view, if somebody who cares speaks up with the
required info I think we should try to continue to support the HP
compilers. Of course if we cannot get to the required information we
shouldn't hold up progress in supporting gcc.
> It looks like we need some
> GCC_DEVELOPERS_DONT_THINK_BEFORE_THEY_CODE_MAP_REG_TO_REGNUM mapping.
> (sorry Dave) Sigh....
>
> Well, let's call it dwarf2_frame_reg_to_regnum().
I'll submit a patch to gdb-patches to implement this for hppa64 shortly.
randolph
next prev parent reply other threads:[~2005-11-27 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200511260253.jAQ2rP7Z021130@hiauly1.hia.nrc.ca>
2005-11-26 9:23 ` Randolph Chung
2005-11-26 15:54 ` Mark Kettenis
2005-11-26 16:52 ` Randolph Chung
2005-11-26 17:32 ` Mark Kettenis
2005-11-26 18:50 ` John David Anglin
2005-11-27 16:30 ` Randolph Chung [this message]
2005-11-26 17:34 ` John David Anglin
2005-11-26 17:20 ` John David Anglin
2005-11-26 17:13 ` John David Anglin
2005-11-26 17:52 ` Mark Kettenis
2005-11-26 18:00 ` John David Anglin
2005-11-26 18:31 ` Mark Kettenis
2005-11-27 4:30 ` John David Anglin
2005-11-27 15:10 ` Randolph Chung
2005-11-27 16:52 ` John David Anglin
2005-11-27 17:42 ` Mark Kettenis
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=4389CC73.9060706@tausq.org \
--to=randolph@tausq.org \
--cc=brobecker@adacore.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.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