This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/48459] [4.6/4.7 Regression] avr: Assertion failure with -gdwarf-2
- From: "rth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 15 Jun 2011 14:41:57 +0000
- Subject: [Bug debug/48459] [4.6/4.7 Regression] avr: Assertion failure with -gdwarf-2
- Auto-submitted: auto-generated
- References: <bug-48459-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48459
--- Comment #26 from Richard Henderson <rth at gcc dot gnu.org> 2011-06-15 14:40:58 UTC ---
(In reply to comment #25)
> (Assuming that backporting implies the emission of DWARF2 CFI) Is it not
> possible to drop DWARF2 CFI feature (which is optional) and still make 4.6x
> build successful? It is quite possible that some target might want to do this.
Um. Why? This is not using dwarf2 cfi for unwinding; that is
still using setjmp. This is using dwarf2 cfi for debugging,
which is exactly what you asked for when you said -gdwarf-2.
If you mean the assembler .cfi directives, you do not need
that in order for the build to succeed. But that is detected
at configure time; if you have an assembler that accepts them
we will emit them, otherwise we'll emit the cfi data as .byte.
If you mean something else, I don't know what it is.