Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tristan Gingold <gingold@adacore.com>,
	       GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH/aarch64] Fix handling of hfa/hva arrays
Date: Wed, 09 Dec 2015 11:23:00 -0000	[thread overview]
Message-ID: <56680F2F.7050408@redhat.com> (raw)
In-Reply-To: <9807AC8E-AB8B-42D5-BEF8-1CF4D5731E28@adacore.com>

On 12/09/2015 11:04 AM, Tristan Gingold wrote:
> Hello,
> 
> the current handling of hfa arrays is not correct: first the length comparison
> is using the size instead of the length so only array of a single float could
> be considered as an hfa.
> 
> Second, where used HFA were only considered as struct/union.  Incorrect
> accessor (like TYPE_NFIELDS) were used on arrays.
> 
> Unfortunately, we don’t have the setup to run the gdb testsuite on that
> processor.  So this patch was only manually tested (using our own
> internal testsuite) on a slightly older version of gdb.

Note there are now 4 Aarch64 Ubuntu machines available on the gcc compile
farm: gcc113-gcc116.

Thanks,
Pedro Alves


  reply	other threads:[~2015-12-09 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 11:04 Tristan Gingold
2015-12-09 11:23 ` Pedro Alves [this message]
2015-12-14 12:59 ` Yao Qi

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=56680F2F.7050408@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.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