This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/49726] New: -g0 file.S -g does not produce debug info
- From: "jan.kratochvil at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 13 Jul 2011 05:23:22 +0000
- Subject: [Bug driver/49726] New: -g0 file.S -g does not produce debug info
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49726
Summary: -g0 file.S -g does not produce debug info
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: jan.kratochvil@redhat.com
Target: x86_64-fedora15-linux-gnu
Build: x86_64-fedora15-linux-gnu
FAIL: gcc (GCC) 4.4.7 20110712 (prerelease)
FAIL: gcc (GCC) 4.5.4 20110712 (prerelease)
FAIL: gcc (GCC) 4.6.2 20110713 (prerelease)
FAIL: gcc (GCC) 4.7.0 20110713 (experimental)
gcc -c -o 1.o 1.c -g: debug info produced
gcc -c -o 1.o 1.S -g: debug info produced
gcc -c -o 1.o -g0 1.c -g: debug info produced
gcc -c -o 1.o -g0 1.S -g: debug info not produced - IMO a bug
Why .c and .S behave differently wrt -g application rules?
Sure for .S there is just the .debug_line relevant.