public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/12753] [3.3/3.4/3.5 regression] Memory corruption in cpp on bad input
Date: Sun, 21 Mar 2004 18:50:00 -0000 [thread overview]
Message-ID: <20040321185027.8113.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031024064638.12753.hjl@lucon.org>
------- Additional Comments From mmitchel at gcc dot gnu dot org 2004-03-21 18:50 -------
I cannot reproduce this problem in GCC 3.4.0.
Is there a more reliable way of reproducing it?
In any case, I'm retargeting this at 3.4.1.
Gaby and I have already agreed that the 3.4.x target milestones take precedence
over the 3.3.x milestones. Gaby, please note that this used to be marked as
targeted at 3.3.4, but is now targeted at 3.4.1.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |gdr at integrable-solutions
| |dot net
Target Milestone|3.3.4 |3.4.1
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12753
next prev parent reply other threads:[~2004-03-21 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-24 6:48 [Bug preprocessor/12753] New: " hjl at lucon dot org
2003-10-24 7:39 ` [Bug preprocessor/12753] " hjl at lucon dot org
2003-10-24 12:55 ` [Bug preprocessor/12753] [3.3,3.4 regression] " ehrhardt at mathematik dot uni-ulm dot de
2003-10-24 16:48 ` [Bug preprocessor/12753] [3.3/3.4 " pinskia at gcc dot gnu dot org
2003-12-20 20:23 ` pinskia at gcc dot gnu dot org
2003-12-24 21:31 ` gdr at gcc dot gnu dot org
2003-12-24 21:37 ` zack at gcc dot gnu dot org
2003-12-28 0:24 ` stl at caltech dot edu
2003-12-28 0:25 ` zack at gcc dot gnu dot org
2004-01-21 4:16 ` [Bug preprocessor/12753] [3.3/3.4/3.5 " gdr at gcc dot gnu dot org
2004-01-21 4:27 ` zack at codesourcery dot com
2004-02-15 12:36 ` gdr at gcc dot gnu dot org
2004-03-21 18:50 ` mmitchel at gcc dot gnu dot org [this message]
2004-06-01 4:26 ` zack at gcc dot gnu dot org
2004-06-09 19:22 ` mmitchel at gcc dot gnu dot org
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=20040321185027.8113.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).