public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Denis Vakatov <vakatov@ncbi.nlm.nih.gov>
To: gcc@gcc.gnu.org
Cc: vakatov@ncbi.nlm.nih.gov
Subject: The 3.4.X line future (for the next half a year)?
Date: Sat, 13 Nov 2004 21:05:00 -0000	[thread overview]
Message-ID: <wo3d5yh5vxr.fsf@ncbi.nlm.nih.gov> (raw)

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). 

  2) Having all (most) major and medium-importance known compiler
     issues taken care of -- in the nearest 3-6 months.  


LYRICS:

    I believe this info can be of great interest not only to us but also to
  other people who cannot upgrade compiler versions too often and therefore
  try to catch the next "great and stable" release of GCC compiler.
    IMHO, 3.4.X is going to be just such a workhorse -- as even the forefather
  of the line, 3.4.0, has been very good to us, and "the great beginning is
  half a battle" :-). Before 3.4, we tried but could not switch to any new
  version -- since 3.0.4 (!). Almost got so desperate as to apply ABI-breaking
  patches for 3.3.X, but 3.4 came and saved us.


Regards and Thanks,
   Denis Vakatov
   NCBI C++ Toolkit:   http:://www.ncbi.nlm.nih.gov/IEB/ToolBox/CPP_DOC/
   National Center for Biotechnology Information
   National Institutes of Health

             reply	other threads:[~2004-11-13 20:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-13 21:05 Denis Vakatov [this message]
2004-11-15 11:18 ` Joe Buck
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=wo3d5yh5vxr.fsf@ncbi.nlm.nih.gov \
    --to=vakatov@ncbi.nlm.nih.gov \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).