public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/14492] [3.4?/3.5? Regression] loc_descriptor_from_tree, in dwarf2out.c:9031
Date: Tue, 31 Aug 2004 11:58:00 -0000 [thread overview]
Message-ID: <20040831115814.13035.qmail@sourceware.org> (raw)
In-Reply-To: <20040308210134.14492.krischik@users.sourceforge.net>
------- Additional Comments From ebotcazou at gcc dot gnu dot org 2004-08-31 11:58 -------
Just to make it clear that the problem is not really fixed on the 3.4 branch,
merely swept under the rug. An --enable-checking build will have 6 failures:
FAIL: gcc.dg/debug/crash1.c -gdwarf-2 (test for excess errors)
FAIL: gcc.dg/debug/crash1.c -gdwarf-2 -O (test for excess errors)
FAIL: gcc.dg/debug/crash1.c -gdwarf-2 -O3 (test for excess errors)
FAIL: gcc.dg/debug/crash1.c -gdwarf-23 (test for excess errors)
FAIL: gcc.dg/debug/crash1.c -gdwarf-23 -O (test for excess errors)
FAIL: gcc.dg/debug/crash1.c -gdwarf-23 -O3 (test for excess errors)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14492
next prev parent reply other threads:[~2004-08-31 11:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 21:01 [Bug ada/14492] New: loc_descriptor_from_tree, bei dwarf2out.c:9031 krischik at users dot sourceforge dot net
2004-03-08 21:46 ` [Bug ada/14492] loc_descriptor_from_tree, in dwarf2out.c:9031 pinskia at gcc dot gnu dot org
2004-03-08 22:44 ` [Bug debug/14492] " charlet at gcc dot gnu dot org
2004-03-09 8:39 ` krischik at users dot sourceforge dot net
2004-04-09 14:50 ` shalla at darkover dot isilm dot com
2004-04-09 15:01 ` [Bug debug/14492] [3.4?/3.5? Regression] " pinskia at gcc dot gnu dot org
2004-06-01 20:58 ` pbrook at gcc dot gnu dot org
2004-06-18 23:58 ` mmitchel at gcc dot gnu dot org
2004-08-24 2:07 ` cvs-commit at gcc dot gnu dot org
2004-08-24 2:10 ` cvs-commit at gcc dot gnu dot org
2004-08-24 2:18 ` mmitchel at gcc dot gnu dot org
2004-08-24 2:21 ` mmitchel at gcc dot gnu dot org
2004-08-31 11:58 ` ebotcazou at gcc dot gnu dot org [this message]
2004-09-20 20:46 ` [Bug debug/14492] [3.4 " pinskia at gcc dot gnu dot org
2004-09-20 20:47 ` pinskia at gcc dot gnu dot org
2004-09-20 20:54 ` pinskia at gcc dot gnu dot org
2004-10-14 21:38 ` rth at gcc dot gnu dot org
2004-10-14 23:28 ` cvs-commit at gcc dot gnu dot org
2004-10-14 23:30 ` cvs-commit at gcc dot gnu dot org
2004-10-14 23:31 ` rth at gcc dot gnu dot org
2005-03-20 23:43 ` pinskia 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=20040831115814.13035.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).