Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: HP/UX 64 need CALL_DUMMY_LOCATION ON_STACK?
Date: Tue, 28 Jan 2003 14:40:00 -0000	[thread overview]
Message-ID: <3E369667.3060904@redhat.com> (raw)
In-Reply-To: <20030128041455.GG6437@gnat.com>


> I believe you are right. I did a bit of archeology, but could not
> find the purpose of this undef.
> 
> Before you added the '#define CALL_DUMMY_LOCATION ON_STACK' when you
> changed the default value for CALL_DUMMY_LOCATION, there was no such
> defined in tm-hppa.h... So the undef was useless, and now seems to
> cause some breakage on hppa64.
> 
> Short of understanding completely the issues at hand, I simply ran the
> testsuite with and without the #undef, and found that that results are
> sensibly better without (ie, to my relief, you guess right about hppa64).
> 
> I have the following change ready:
> 
> 2003-01-28  J. Brobecker  <brobecker@gnat.com>
> 
> 	* config/pa/tm-hppa64.h (CALL_DUMMY_LOCATION): Remove #undef
> 	causing some regressions due to a change in the default value
> 	for this macro.

Thanks!  Definitly check this in.

Andrew



  reply	other threads:[~2003-01-28 14:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20  2:08 Andrew Cagney
2003-01-20  3:04 ` Joel Brobecker
2003-01-20  4:27   ` Andrew Cagney
2003-01-28  4:15     ` Joel Brobecker
2003-01-28 14:40       ` Andrew Cagney [this message]
2003-01-30  5:49         ` Joel Brobecker

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=3E369667.3060904@redhat.com \
    --to=ac131313@redhat.com \
    --cc=brobecker@gnat.com \
    --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