Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Thiago Jung Bauermann <bauerman@br.ibm.com>
Cc: gdb-patches ml <gdb-patches@sourceware.org>
Subject: Re: [RFA] Change AUXV bit checked to decide the size of the FPSCR
Date: Wed, 25 Mar 2009 16:54:00 -0000	[thread overview]
Message-ID: <20090325163938.GY9472@adacore.com> (raw)
In-Reply-To: <1237819493.25721.38.camel@localhost.localdomain>

(Thiago - I like the quality of the work you produce, very nice!)

> For this reason, I'm changing GDB to check for DFP to decide what is the
> size of the FPSCR (it changed from 32 bits to 64 bits with ISA 2.05 and
> newer). Since for now the only higher bits used are for Decimal Floating
> Point, I am changing the code to check the DFP bit in AUXV.

This sounds more like a work-around than a real fix. I don't mind
your approach, but I think it deserves a clear comment in the code
where you use that flag to determine the size of your registers.

For the record, another solution that you probably considered was to
check for PPC_FEATURE_ARCH_2_05 *or* PPC_FEATURE_ARCH_2_06, but I can
see how this might become cumbersome as future revisions get added.

> gdb/
> 	* ppc-linux-nat.c (PPC_FEATURE_ARCH_2_05): Remove #define.
> 	(PPC_FEATURE_HAS_DFP): New #define.
> 	(ppc_linux_read_description): Check for DFP feature instead of
> 	ISA 2.05 to decide on size of the FPSCR.
> 
> gdbserver/
> 	* linux-ppc-low.c (PPC_FEATURE_ARCH_2_05): Remove #define.
> 	(PPC_FEATURE_HAS_DFP): New #define.
> 	(ppc_arch_setup): Check for DFP feature instead of ISA 2.05 to decide on
> 	size of the FPSCR.

Both OK with the requested comments added.

-- 
Joel


  reply	other threads:[~2009-03-25 16:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-23 15:22 Thiago Jung Bauermann
2009-03-25 16:54 ` Joel Brobecker [this message]
2009-03-25 21:27   ` Thiago Jung Bauermann

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=20090325163938.GY9472@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bauerman@br.ibm.com \
    --cc=gdb-patches@sourceware.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