Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: heads up: GDB 7.7 official release Wed Jan 29th (tomorrow)
Date: Tue, 28 Jan 2014 18:07:00 -0000	[thread overview]
Message-ID: <20140128180722.GJ4101@adacore.com> (raw)
In-Reply-To: <201401281749.s0SHn5dA019738@d06av02.portsmouth.uk.ibm.com>

> I'm certainly aware that this comes in at a very late time, but
> given the timing of when powerpc64le-linux support shows up in
> the other parts of the core toolchain (binutils 2.24, gcc 4.9,
> glibc 2.19) it would be really nice if GDB 7.7 also had support,
> to complete the picture ...

Outch.

> On the other hand, it would certainly be preferable to allow for
> at least a couple of days before checking the series in to give
> people a chance to comment, so it seems unlikely this could be
> in place in the branch by tomorrow.

I don't know of any reason that would force us to release tomorrow.
The last 2-3 weeks of pre-release testing having been fairly quiet,
we had no real reason to wait either.

> So I guess I'm wondering if you see workable options to still
> get powerpc64le-linux support into a release in the near future ...
> Maybe we could do a 7.7.1 ?

I'm a bit uncomfortable including support for a new target like that
without more testing, particularly since the changes affects files
already in use by other ports. I had a quick look, and perhaps the
changes can be reviewed well enough to convince ourselves that they
are indeed safe enough for the branch.

Here is what I propose:

  1. We delay the release to Monday (Feb 3rd).

  2. During that time frame, let's try to get the changes reviewed
     by at least one more GM - it might be me.

It would be good to get a sense of when people think gcc-4.9 is going
to come out. Last I looked, the branch hadn't been created yet.
Perhaps, one option is to schedule 7.8 to coincide with gcc-4.9
(or slightly before, if we'd like to).

Cheers,
-- 
Joel


  reply	other threads:[~2014-01-28 18:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  2:31 Joel Brobecker
2014-01-28  4:02 ` Sergio Durigan Junior
2014-01-28 14:59   ` Joel Brobecker
2014-01-28 17:49 ` Ulrich Weigand
2014-01-28 18:07   ` Joel Brobecker [this message]
2014-01-28 18:22     ` Ulrich Weigand
2014-01-29  8:14       ` Joel Brobecker
2014-01-29  9:31         ` Mark Kettenis
2014-01-29 18:57           ` Ulrich Weigand
2014-01-29 11:05 Tobias Burnus

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=20140128180722.GJ4101@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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