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: "anitha.boyapati at atmel dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 13 Jun 2011 07:57:11 +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 #15 from Anitha Boyapati <anitha.boyapati at atmel dot com> 2011-06-13 07:55:19 UTC ---
(In reply to comment #14)
> (In reply to comment #13)
>
> > Can you change the state to NEW and raise the severity to blocker? I don't have
> > required privileges.
>
> I've set state to NEW, but raised the severity to MAJOR. You need to understand
> that the severity is for the entire GCC project and the AVR target is not even
> a "secondary" target, even though it might be critical for Atmel.
Correction: Not for Atmel and I am definitely not representing it.
I am going by the definition given in bug's life cycle. A blocker is described
as some bug which blocks development and/or testing work. The current bug does
when DWARF2 is enabled. But as you said, if more parameters are to be
considered, yes, I need to understand them.