public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "anitha.boyapati at atmel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/48459] [4.6/4.7 Regression] avr: Assertion failure with -gdwarf-2
Date: Mon, 13 Jun 2011 07:57:00 -0000 [thread overview]
Message-ID: <bug-48459-4-EDOoFHyCjn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2011-06-13 7:57 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 11:56 [Bug other/48459] New: " avr at gjlay dot de
2011-04-06 0:20 ` [Bug debug/48459] [4.7 Regression] " pinskia at gcc dot gnu.org
2011-04-21 10:03 ` gjl at gcc dot gnu.org
2011-04-22 7:45 ` [Bug debug/48459] [4.6/4.7 " gjl at gcc dot gnu.org
2011-06-09 14:01 ` anitha.boyapati at atmel dot com
2011-06-09 14:19 ` jason at gcc dot gnu.org
2011-06-09 16:54 ` anitha.boyapati at atmel dot com
2011-06-09 17:01 ` anitha.boyapati at atmel dot com
2011-06-09 18:10 ` jason at gcc dot gnu.org
2011-06-10 4:15 ` anitha.boyapati at atmel dot com
2011-06-10 5:24 ` jason at gcc dot gnu.org
2011-06-10 7:39 ` anitha.boyapati at atmel dot com
2011-06-10 16:25 ` jason at gcc dot gnu.org
2011-06-13 6:54 ` anitha.boyapati at atmel dot com
2011-06-13 7:15 ` anitha.boyapati at atmel dot com
2011-06-13 7:31 ` eric.weddington at atmel dot com
2011-06-13 7:57 ` anitha.boyapati at atmel dot com [this message]
2011-06-13 14:46 ` jason at gcc dot gnu.org
2011-06-13 19:29 ` rth at gcc dot gnu.org
2011-06-14 7:01 ` anitha.boyapati at atmel dot com
2011-06-14 9:11 ` gjl at gcc dot gnu.org
2011-06-14 9:48 ` gjl at gcc dot gnu.org
2011-06-14 13:28 ` rth at gcc dot gnu.org
2011-06-14 13:32 ` rth at gcc dot gnu.org
2011-06-14 16:32 ` gjl at gcc dot gnu.org
2011-06-14 19:14 ` rth at gcc dot gnu.org
2011-06-14 19:18 ` rth at gcc dot gnu.org
2011-06-15 2:38 ` anitha.boyapati at atmel dot com
2011-06-15 14:42 ` rth at gcc dot gnu.org
2011-06-16 6:35 ` anitha.boyapati at atmel dot com
2011-06-16 6:38 ` anitha.boyapati at atmel dot com
2011-06-16 13:55 ` rth at gcc dot gnu.org
2011-06-17 7:09 ` anitha.boyapati at atmel dot com
2011-06-17 15:52 ` rth at gcc dot gnu.org
2011-06-17 16:06 ` rth at gcc dot gnu.org
2011-06-20 5:02 ` anitha.boyapati at atmel 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=bug-48459-4-EDOoFHyCjn@http.gcc.gnu.org/bugzilla/ \
--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).