public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19149] [4.0 Regression] seg fault on invalid code
Date: Fri, 24 Dec 2004 18:33:00 -0000 [thread overview]
Message-ID: <20041224183333.24810.qmail@sourceware.org> (raw)
In-Reply-To: <20041224180135.19149.pinskia@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-24 18:33 -------
I think this was caused by:
2004-06-23 Mark Mitchell <mark@codesourcery.com>
* Make-lang.in (cp/lex.o): Do not depend on cp/lex.h.
(cp/decl.o): Likewise.
(cp/decl2.o): Likewise.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |mmitchel at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19149
next prev parent reply other threads:[~2004-12-24 18:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 18:01 [Bug c++/19149] New: " pinskia at gcc dot gnu dot org
2004-12-24 18:02 ` [Bug c++/19149] " pinskia at gcc dot gnu dot org
2004-12-24 18:03 ` pinskia at gcc dot gnu dot org
2004-12-24 18:25 ` pinskia at gcc dot gnu dot org
2004-12-24 18:33 ` pinskia at gcc dot gnu dot org [this message]
2004-12-27 18:28 ` mmitchel at gcc dot gnu dot org
2004-12-27 19:03 ` cvs-commit at gcc dot gnu dot org
2004-12-27 19:04 ` 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=20041224183333.24810.qmail@sourceware.org \
--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).