From: Joe Buck <Joe.Buck@synopsys.COM>
To: Denis Vakatov <vakatov@ncbi.nlm.nih.gov>
Cc: gcc@gcc.gnu.org
Subject: Re: The 3.4.X line future (for the next half a year)?
Date: Mon, 15 Nov 2004 11:18:00 -0000 [thread overview]
Message-ID: <20041114211020.A5246@synopsys.com> (raw)
In-Reply-To: <wo3d5yh5vxr.fsf@ncbi.nlm.nih.gov>; from vakatov@ncbi.nlm.nih.gov on Sat, Nov 13, 2004 at 03:35:28PM -0500
On Sat, Nov 13, 2004 at 03:35:28PM -0500, Denis Vakatov wrote:
> QUESTION: (to the GCC developers/maintainers of 3.4.X line)
>
> What are your [ballpark, subjective, gut-feeling] expectations about:
>
> 1) The schedule of the future 3.4.X bug-fix releases (how often and
> how many and for how long).
Here's just one view.
There's no set schedule; I think you can be reasonably confident that
there will be at least one more release (though this is not a promise);
after that, it depends on volunteer availability.
> 2) Having all (most) major and medium-importance known compiler
> issues taken care of -- in the nearest 3-6 months.
You can be certain that this will NOT happen in the 3.4.x series. There
will be bug fixes, but all of the problems are not going to be solved.
In particular, the performance and code quality problems are going to be
addressed as part of 4.0, not 3.4. If fixes cannot be backported without
major changes, they would probably be considered too risky.
next prev parent reply other threads:[~2004-11-15 5:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-13 21:05 Denis Vakatov
2004-11-15 11:18 ` Joe Buck [this message]
2004-11-15 21:49 ` Mark Mitchell
2004-11-16 3:57 Benjamin Kosnik
2004-11-16 6:41 ` Mark Mitchell
2004-11-23 1:13 ` Gabriel Dos Reis
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=20041114211020.A5246@synopsys.com \
--to=joe.buck@synopsys.com \
--cc=gcc@gcc.gnu.org \
--cc=vakatov@ncbi.nlm.nih.gov \
/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).