Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>,
	GDB Patches <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: Request for 8.2, SVE cores && adding SVE to NEWS file etc
Date: Thu, 16 Aug 2018 16:17:00 -0000	[thread overview]
Message-ID: <843fee7a-1738-4147-256f-e1fc7950fe18@redhat.com> (raw)
In-Reply-To: <BB8CBC76-B347-43D9-9042-110598C87048@arm.com>

On 08/15/2018 10:31 AM, Alan Hayward wrote:
> Wasn’t sure if this was the best place to ask.
> 
> 1) Is 8.2 still open to new functionality? It’d be really useful to have core support for Aarch64 SVE in 8.2
> (Given SVE is supported in 8.2, I guess you could argue it’s a bug fix :). )
> Currently in 8.2, GDB will just ignore the SVE parts of a core file.

Not usually, but there have been exceptions evaluated on a case by case basis.

> 
> The four commits are:
> (Earliest patch is obv, second is a mechanical change across many files, the final two are aarch64 only)
> 
> 0c76e06d5c   2 days ago Alan Hayward    Parse SVE registers in aarch64 core file reading/writing
> b7fd65b9dc   2 days ago Alan Hayward    Detect SVE when reading aarch64 core files
> a616bb9450   2 days ago Alan Hayward    Split size in regset section iterators
> dbd534fee4   5 days ago Alan Hayward    Rename size in get_core_register_sectio

I haven't looked at the patches, but in principle, I'd support it,
from the standpoint that since we're adding SVE support, might as well
add all of it.  Also, speaking with my Fedora/RHEL had on, we'd likely end
up backporting them too.  Can you give a guesstimate of the risk those
patches bring in to other ports?  I'd assume they'd be pretty self contained.

> 
> 
> 2) I’ve spotted that Aarch64 SVE support should probably be mentioned in the NEWS file.
> Are there any other documentation type files that need updating alongside?

Well, the user manual, if there were any changes to it.  

If the SVE support included any new XML target description feature,
that should be mentioned in the manual.

Thanks,
Pedro Alves


  reply	other threads:[~2018-08-16 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15  9:31 Alan Hayward
2018-08-16 16:17 ` Pedro Alves [this message]
2018-08-17  9:26   ` Alan Hayward
2018-08-21 13:16     ` Joel Brobecker
2018-08-21 14:34       ` 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=843fee7a-1738-4147-256f-e1fc7950fe18@redhat.com \
    --to=palves@redhat.com \
    --cc=Alan.Hayward@arm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.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