public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mec dot gnu at mindspring dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/13974] [3.5 regression] bad line marker in debug info
Date: Sun, 04 Apr 2004 19:23:00 -0000 [thread overview]
Message-ID: <20040404192341.9036.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040202092323.13974.mec.gnu@mindspring.com>
------- Additional Comments From mec dot gnu at mindspring dot com 2004-04-04 19:23 -------
gcc gcc-3_4-branch 20040330 works correctly on my test programs. Good job.
But it is still broken in gcc HEAD 20040330.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13974
next prev parent reply other threads:[~2004-04-04 19:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 9:23 [Bug debug/13974] New: [3.4/3.5 " mec dot gnu at mindspring dot com
2004-02-02 9:24 ` [Bug debug/13974] " mec dot gnu at mindspring dot com
2004-02-02 9:24 ` mec dot gnu at mindspring dot com
2004-02-02 9:25 ` mec dot gnu at mindspring dot com
2004-02-02 9:28 ` pinskia at gcc dot gnu dot org
2004-02-03 5:35 ` drow at gcc dot gnu dot org
2004-02-03 8:27 ` pinskia at gcc dot gnu dot org
2004-03-01 1:52 ` mmitchel at gcc dot gnu dot org
2004-03-11 5:07 ` mmitchel at gcc dot gnu dot org
2004-03-11 17:49 ` jh at suse dot cz
2004-03-13 22:10 ` jh at suse dot cz
2004-03-14 1:29 ` drow at false dot org
2004-03-14 10:12 ` jh at suse dot cz
2004-03-14 17:31 ` drow at false dot org
2004-03-14 17:42 ` jh at suse dot cz
2004-03-25 16:45 ` cvs-commit at gcc dot gnu dot org
2004-03-25 19:31 ` [Bug debug/13974] [3.5 " pinskia at gcc dot gnu dot org
2004-04-04 19:23 ` mec dot gnu at mindspring dot com [this message]
2004-08-27 14:47 ` giovannibajo at libero dot it
2004-09-22 18:23 ` [Bug debug/13974] [4.0 " pinskia at gcc dot gnu dot org
2004-09-30 21:26 ` cvs-commit at gcc dot gnu dot org
2004-09-30 21:27 ` hubicka at gcc dot gnu dot org
2004-10-13 17:15 ` mec dot gnu at mindspring dot com
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=20040404192341.9036.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).