Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Mark Kettenis <mark.kettenis@xs4all.nl>
Subject: Re: $zero on alpha should always be available
Date: Tue, 24 May 2011 11:16:00 -0000	[thread overview]
Message-ID: <201105241216.07135.pedro@codesourcery.com> (raw)
In-Reply-To: <20110524044418.GC4909@adacore.com>

On Tuesday 24 May 2011 05:44:18, Joel Brobecker wrote:
> > Here's what I came up with by inspection.  I have no alpha machine to test
> > this on.  The alpha-nat.c change would need
> > checking on an alpha running OSF if we wanted to test this...
> 
> Thanks, Pedro.  I will try to test this tomorrow. I think Tru64 is
> one of the systems where expect or tcl no longer work for me, so
> I might not be able to run the testsuite. But worse case scenario,
> I can try running it against AdaCore's testsuite.

Thanks Joel.  Even if you can't run any testsuite,
confirming that nothing broke in an obvious way, and
that $zero appears as 0 to 'p $zero' or "info all-registers",
and not as <unavailable> with a running program would be a good
test already.  The alpha-nat.c change is trying to make 
the same fix for loading alpha-OSF cores.

> 
> > 2011-05-23  Pedro Alves  <pedro@codesourcery.com>
> > 
> > 	gdb/
> > 	* alpha-tdep.c (alpha_cannot_fetch_register): Don't return true
> > 	for ALPHA_ZERO_REGNUM.
> > 	(alpha_supply_int_regs): Explicitly supply zero as the value for
> > 	ALPHA_ZERO_REGNUM in the register cache.
> > 	* alpha-nat.c (fetch_osf_core_registers): Ditto.
> 
> 

-- 
Pedro Alves


  reply	other threads:[~2011-05-24 11:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 19:20 [PATCH] %g0 on sparc " Mark Kettenis
2011-05-22 11:17 ` Pedro Alves
2011-05-23 17:36   ` $zero on alpha " Pedro Alves
2011-05-24  4:44     ` Joel Brobecker
2011-05-24 11:16       ` Pedro Alves [this message]
2011-05-25 20:51         ` Joel Brobecker
2011-05-26 14:16           ` Pedro Alves

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=201105241216.07135.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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