Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias.burnus@physik.fu-berlin.de>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: heads up: GDB 7.7 official release Wed Jan 29th (tomorrow)
Date: Wed, 29 Jan 2014 11:05:00 -0000	[thread overview]
Message-ID: <20140129110450.GA2713@physik.fu-berlin.de> (raw)

Regarding GCC 4.9:

Joel Brobecker wrote:
> 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).

Well, since a couple of years, the GCC branching happens when the
first release candidate is build. The actual release is then one or
two weeks later - depending how many P1 bugs or other issues are
found. Regarding the release time: In the last few years, GCC was
usually released in March, April or May.


In case of GCC 4.8.0: RC1 plus branching March 16, 4.8.0 release
March 21 (announced: March 22). See also
http://gcc.gnu.org/develop.html#timeline

Regarding 4.9: My guess would be that it will take a bit longer
this year due to some larger changes late in the game. Last status
report (1 month ago): http://gcc.gnu.org/ml/gcc/2013-12/msg00203.html
See also "Serious regressions" for 4.9 on http://gcc.gnu.org/

Tobias


             reply	other threads:[~2014-01-29 11:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 11:05 Tobias Burnus [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2014-01-29  9:31         ` Mark Kettenis
2014-01-29 18:57           ` Ulrich Weigand

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=20140129110450.GA2713@physik.fu-berlin.de \
    --to=tobias.burnus@physik.fu-berlin.de \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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