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: Wed, 29 Jan 2014 08:14:00 -0000 [thread overview]
Message-ID: <20140129081408.GS4101@adacore.com> (raw)
In-Reply-To: <201401281822.s0SIMWLd002802@d06av02.portsmouth.uk.ibm.com>
> I would certainly appreciate that -- thanks!
>
> As to changes in other ports, I think it should be pretty clear
> that non-PowerPC platforms cannot really be affected. (There are
> some changes to common code in the 11/11 patch, but that shouldn't
> affect any platform that do not define gdbarch_skip_entrypoint.)
>
> As to other PowerPC platforms, I've tested powerpc64-linux quite a
> bit -- I would be happy to also run a regression test on a 32-bit
> Linux and on AIX.
OK, I've had a chance to review the patches, and I am definitely
hesitating. I agree that they can only affect PowerPC. If you feel
very confident about the patches and want to take responsibility,
I will go with your call. Advice from the other GMs would also be
useful.
My preference goes towards getting this code in the master branch
first, release 7.7 without it, and then re-evaluate. If proven after
an observation period to be stable in master, we can elect to backport
the code to 7.7 in time for 7.7.1. But if people prefer, we can also
accelerate the schedule for 7.8.
--
Joel
next prev parent reply other threads:[~2014-01-29 8:14 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
2014-01-28 18:22 ` Ulrich Weigand
2014-01-29 8:14 ` Joel Brobecker [this message]
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=20140129081408.GS4101@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