public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pebbles at riseup dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/57631] [patch] spurious warning for avr interrupts with asm labels
Date: Fri, 21 Jun 2013 18:04:00 -0000 [thread overview]
Message-ID: <bug-57631-4-4aE3llbjWS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57631-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57631
pebbles at riseup dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|pebbles at riseup dot net |unassigned at gcc dot gnu.org
--- Comment #9 from pebbles at riseup dot net ---
I would like to learn to find out if this is a bug and contribute a fix to the
gcc sources. At the moment building gcc loads my computer for a day, and it is
difficult to develop on. I plan to pursue this when I am set up better, but if
anybody else ever cares about it they should look at it.
As far as I can tell the patch I attached is good but I haven't turned my test
into a testcase or read the gcc development docs yet.
next prev parent reply other threads:[~2013-06-21 18:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 22:27 [Bug target/57631] New: " pebbles at riseup dot net
2013-06-16 23:19 ` [Bug target/57631] " pebbles at riseup dot net
2013-06-17 0:08 ` pebbles at riseup dot net
2013-06-21 10:48 ` [Bug target/57631] [patch] " gjl at gcc dot gnu.org
2013-06-21 12:13 ` pebbles at riseup dot net
2013-06-21 16:15 ` gjl at gcc dot gnu.org
2013-06-21 16:34 ` pebbles at riseup dot net
2013-06-21 18:04 ` pebbles at riseup dot net [this message]
2013-06-21 18:34 ` gjl at gcc dot gnu.org
2013-06-26 1:40 ` pebbles at riseup dot net
2013-07-11 8:53 ` gjl at gcc dot gnu.org
2014-03-05 14:07 ` [Bug target/57631] Use assembler name for sanity checking of ISR names provided it is set mhlavink at redhat 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-57631-4-4aE3llbjWS@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).