From: Andrew Cagney <cagney@gnu.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch/rfa] hppa-linux target, 2nd try
Date: Wed, 28 Apr 2004 15:58:00 -0000 [thread overview]
Message-ID: <408FD4B0.1000706@gnu.org> (raw)
In-Reply-To: <20040424192614.GD2923@tausq.org>
> 2004-04-24 Randolph Chung <tausq@debian.org>
>
> * configure.host (hppa*-*-linux*): New target.
> * configure.tgt (hppa*-*-linux*): Likewise.
> * hppa-tdep.c (hppa_gdbarch_init): Set cannot_fetch_register, move
> gdbarch_init_osabi() call earlier so that osabi-specific frame
> unwinders can be registered first.
> * config/djgpp/fnchange.lst: Add entries for hppa-linux-tdep.c and
> * config/pa/tm-hppa.h: Add definitions of some register numbers.
> * config/pa/linux.mh: New file.
> * config/pa/linux.mt: New file.
> * config/pa/nm-linux.h: New file.
> * config/pa/xm-linux.h: New file.
> * hppa-linux-nat.c: New file.
> * hppa-linux-tdep.c: New file.
This is all ok.
> +static struct insn_pattern hppa_sigtramp[] = {
> + /* ldi 0, %r25 or ldi 1, %r25 */
> + { 0x34190000, 0xfffffffd },
> + /* ldi __NR_rt_sigreturn, %r20 */
> + { 0x3414015a, 0xffffffff },
> + /* be,l 0x100(%sr2, %r0), %sr0, %r31 */
> + { 0xe4008200, 0xffffffff },
> + /* nop */
> + { 0x08000240, 0xffffffff },
> + { 0, 0 }
> +};
hmm, perhaps the mask can be integrated into tramp-frame.[hc], anyone?
Andrew
next prev parent reply other threads:[~2004-04-28 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-24 19:26 Randolph Chung
2004-04-25 0:25 ` Joel Brobecker
2004-04-25 0:30 ` Randolph Chung
2004-04-28 15:54 ` Andrew Cagney
2004-04-25 6:07 ` Randolph Chung
2004-04-28 15:58 ` Andrew Cagney [this message]
2004-04-28 16:00 ` Randolph Chung
2004-04-28 20:53 ` 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=408FD4B0.1000706@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.org \
/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