public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Alan Hayward <Alan.Hayward@arm.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
	       Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	       Sergio Durigan Junior <sergiodj@redhat.com>,
	       Andrew Burgess <andrew.burgess@embecosm.com>,
	       GDB Patches <gdb-patches@sourceware.org>, nd <nd@arm.com>
Subject: Re: GDB 8.2 branch 2018-06-11 Update
Date: Tue, 12 Jun 2018 12:59:00 -0000	[thread overview]
Message-ID: <92cfc18856f512ca719894d854d88dc9@polymtl.ca> (raw)
In-Reply-To: <0B648932-A474-461D-8CD8-41189FE3A19F@arm.com>

On 2018-06-12 04:29, Alan Hayward wrote:
> Most of the SVE patches are in now. I’ve just got four remaining:
> 
> [PATCH v2 02/10] Add Aarch64 SVE Linux headers
> https://sourceware.org/ml/gdb-patches/2018-06/msg00220.html
> - Simon wanted to check with FSF people if it’s ok to include Linux 
> headers.

Hi Alan,

I'm not sure if you saw this reply here?

https://sourceware.org/ml/gdb-patches/2018-06/msg00219.html

Essentially, I'm suggesting we keep things simple if we want to get the 
SVE support in 8.2 and don't include the headers.  It would require 
users to build against the headers of a recent enough kernel, when 
building for AArch64 native.  I'm waiting for your answer on that.

Simon

  reply	other threads:[~2018-06-12 12:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 22:56 Joel Brobecker
2018-06-12  0:19 ` Sergio Durigan Junior
2018-06-12  8:29 ` Alan Hayward
2018-06-12 12:59   ` Simon Marchi [this message]
2018-06-12 21:57 ` Philippe Waroquiers
2018-06-19  6:07 ` Tom Tromey
2018-06-22 14:21   ` Joel Brobecker
2018-06-22 20:37     ` Tom Tromey

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=92cfc18856f512ca719894d854d88dc9@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=Alan.Hayward@arm.com \
    --cc=andrew.burgess@embecosm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=nd@arm.com \
    --cc=philippe.waroquiers@skynet.be \
    --cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).