From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Markus Henschel <markus.henschel@yager.de>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Questions before submitting a bug report
Date: Tue, 03 Jan 2012 16:55:00 -0000 [thread overview]
Message-ID: <CAH6eHdS232Gu08nVcqROe+=AEm2Z=Mpe+C9DCYri38aVp4vnNA@mail.gmail.com> (raw)
In-Reply-To: <B6A6EF22B0D16146BD127139E7667DDB1625D00DD1@hermes.corp.yager.de>
On 3 January 2012 15:02, Markus Henschel wrote:
> My second question is if it makes any sense to submit this bug if it's against gcc version 4.2.4. I still have to use this compiler version but the bug seems to have vanished in version 4.3.3. Is 4.2.4 still maintained?
No, as shown on the gcc.gnu.org home page, the oldest maintained
release series is GCC 4.4
prev parent reply other threads:[~2012-01-03 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 15:02 Markus Henschel
2012-01-03 15:06 ` Andrew Haley
2012-01-03 15:23 ` Markus Henschel
2012-01-03 15:25 ` Andrew Haley
2012-01-03 15:26 ` Andrew Haley
2012-01-03 15:39 ` Markus Henschel
2012-01-03 15:52 ` Andrew Haley
2012-01-04 10:08 ` Markus Henschel
2012-01-05 23:00 ` Kalle Olavi Niemitalo
2012-01-03 16:55 ` Jonathan Wakely [this message]
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='CAH6eHdS232Gu08nVcqROe+=AEm2Z=Mpe+C9DCYri38aVp4vnNA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=markus.henschel@yager.de \
/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).