public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mec at shout dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/12267] [3.4 regression] function-at-a-time generates stabs in bad order
Date: Sun, 30 Nov 2003 17:48:00 -0000 [thread overview]
Message-ID: <20031130174843.28722.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030912184752.12267.mec@shout.net>
------- Additional Comments From mec at shout dot net 2003-11-30 17:48 -------
This bug still happens with gcc HEAD 2003-11-29 16:28:31 UTC.
Here's an excerpt from a recent z0.s, the result of "gcc -gstabs+ -O2 -S z0.c"
with gcc HEAD 2003-11-29 16:28:31 UTC. (Other info: binutils 2.14, native
i686-pc-linux-gnu, red hat 8.0).
.LM15:
leave
xorl %eax, %eax
ret
.size main, .-main
.stabs "factorial:F(0,1)",36,0,13,factorial
.Lscope1:
.stabs "",36,0,0,.Lscope1-main
.text
.stabs "",100,0,0,.Letext
.Letext:
.section .note.GNU-stack,"",@progbits
.ident "GCC: (GNU) 3.4 20031129 (experimental)"
The ".stabs" for factorial still appears at the end of "main", right after
".size main, .-main"
Also, if you look at gcc/ChangeLog, only half of msg01167.html was committed to
gcc HEAD.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12267
next prev parent reply other threads:[~2003-11-30 17:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 18:50 [Bug debug/12267] New: " mec at shout dot net
2003-09-12 18:52 ` [Bug debug/12267] " mec at shout dot net
2003-09-12 18:53 ` mec at shout dot net
2003-09-12 18:54 ` mec at shout dot net
2003-09-12 18:54 ` mec at shout dot net
2003-09-12 19:06 ` bangerth at dealii dot org
2003-09-12 19:11 ` bangerth at dealii dot org
2003-09-12 21:02 ` mec at shout dot net
2003-09-18 4:26 ` pinskia at gcc dot gnu dot org
2003-11-29 2:06 ` pinskia at gcc dot gnu dot org
2003-11-30 17:48 ` mec at shout dot net [this message]
2003-12-01 6:45 ` pinskia at gcc dot gnu dot org
2003-12-01 19:07 ` mec at shout dot net
2003-12-01 19:12 ` pinskia at gcc dot gnu dot org
2003-12-01 19:33 ` zack at codesourcery dot com
2003-12-06 9:29 ` pinskia at gcc dot gnu dot org
2003-12-29 17:50 ` pinskia at gcc dot gnu dot org
2004-01-06 5:14 ` pinskia at gcc dot gnu dot org
2004-03-16 20:57 ` [Bug debug/12267] [3.4/3.5 " zack at gcc dot gnu dot org
2004-03-21 17:55 ` mmitchel at gcc dot gnu dot org
2004-03-23 23:48 ` cvs-commit at gcc dot gnu dot org
2004-03-23 23:51 ` [Bug debug/12267] [3.4 " zack at gcc dot gnu dot org
2004-06-01 4:23 ` zack at gcc dot gnu dot org
2004-06-12 22:12 ` 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=20031130174843.28722.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).