Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com, Richard.Earnshaw@arm.com
Subject: Re: PATCH multi-arch GET_LONGJMP_TARGET
Date: Wed, 20 Feb 2002 02:49:00 -0000	[thread overview]
Message-ID: <200202201044.KAA06258@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Tue, 19 Feb 2002 10:41:38 GMT." <200202191041.KAA18603@cam-mail2.cambridge.arm.com>


> Thinking about it, the cleanest way to handle this for now is to change 
> the test for a definition of JB_PC, since unless that is defined the code 
> won't compile, and even if it did it would give the wrong answer.
> 
> As far as I can tell, apart from i386, only two further ports define 
> GET_LONGJMP_TARGET: arc and sparc.  Arc seems never to use the code 
> (there's only one .h file for that port and it doesn't define 
> GET_LONGJMP_TARGET or JB_PC); Sparc seems to define it for pretty much all 
> configurations I can think of.
> R.
> 
> <date>  Richard Earnshaw  <rearnsha@arm.com>
> 
> 	* arc-tdep.c (get_longjmp_target): Only compile this function if
> 	JB_PC is defined.
> 	* sparc-tdep.c (get_longjmp_target): Likewise.

I've committed this, given that it was potentially breaking these targets 
by not having this change.

R.


      reply	other threads:[~2002-02-20 10:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-18  5:38 Richard Earnshaw
2002-02-19  0:48 ` Pierre Muller
2002-02-19  2:14   ` Richard Earnshaw
2002-02-19  2:42     ` Richard Earnshaw
2002-02-20  2:49       ` Richard Earnshaw [this message]

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=200202201044.KAA06258@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=muller@cerbere.u-strasbg.fr \
    /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