public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jiez at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44290] [4.5 Regression] __naked attribute is broken
Date: Fri, 23 Jul 2010 14:52:00 -0000 [thread overview]
Message-ID: <20100723145229.8483.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44290-10179@http.gcc.gnu.org/bugzilla/>
------- Comment #23 from jiez at gcc dot gnu dot org 2010-07-23 14:52 -------
Set the status to FIXED.
--
jiez at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44290
next prev parent reply other threads:[~2010-07-23 14:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 6:26 [Bug tree-optimization/44290] New: arm linux kernel crahes when built with -fipa-sra raj dot khem at gmail dot com
2010-05-27 7:07 ` [Bug tree-optimization/44290] " raj dot khem at gmail dot com
2010-05-27 7:13 ` raj dot khem at gmail dot com
2010-05-27 10:41 ` [Bug tree-optimization/44290] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-05-27 17:26 ` raj dot khem at gmail dot com
2010-05-27 17:27 ` raj dot khem at gmail dot com
2010-05-28 11:49 ` mikpe at it dot uu dot se
2010-05-28 22:03 ` mikpe at it dot uu dot se
2010-05-29 11:36 ` mikpe at it dot uu dot se
2010-05-29 11:43 ` [Bug target/44290] [4.5 Regression] arm linux kernel crahes when built with -fipa-sra, __naked attribute is broken rguenth at gcc dot gnu dot org
2010-05-29 11:47 ` rguenth at gcc dot gnu dot org
2010-05-29 11:50 ` rguenth at gcc dot gnu dot org
2010-05-29 13:30 ` Andrew Pinski
2010-05-29 13:30 ` pinskia at gmail dot com
2010-05-29 14:27 ` mikpe at it dot uu dot se
2010-05-29 14:40 ` mikpe at it dot uu dot se
2010-05-29 14:45 ` [Bug target/44290] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-05-29 14:46 ` rguenth at gcc dot gnu dot org
2010-05-29 14:47 ` mikpe at it dot uu dot se
2010-05-29 18:00 ` mikpe at it dot uu dot se
2010-05-30 5:58 ` raj dot khem at gmail dot com
2010-05-30 6:55 ` raj dot khem at gmail dot com
2010-05-30 17:04 ` rguenth at gcc dot gnu dot org
2010-07-23 14:48 ` jiez at gcc dot gnu dot org
2010-07-23 14:51 ` jiez at gcc dot gnu dot org
2010-07-23 14:52 ` jiez at gcc dot gnu dot org [this message]
2010-07-26 8:05 ` [Bug target/44290] [4.5 only] " ramana at gcc dot gnu dot org
2010-07-26 14:38 ` jiez at gcc dot gnu dot org
2010-07-27 17:34 ` jiez at gcc dot gnu dot org
2010-07-31 9:35 ` rguenth at gcc dot gnu dot org
[not found] <bug-44290-4@http.gcc.gnu.org/bugzilla/>
2010-12-15 22:11 ` [Bug target/44290] [4.5 regression] " belyshev at depni dot sinp.msu.ru
2010-12-16 3:06 ` jiez at gcc dot gnu.org
2010-12-16 13:08 ` rguenth at gcc dot gnu.org
2010-12-16 20:47 ` belyshev at depni dot sinp.msu.ru
2010-12-16 20:50 ` belyshev at depni dot sinp.msu.ru
2010-12-21 4:16 ` jiez at gcc dot gnu.org
2011-04-10 10:27 ` rguenth at gcc dot gnu.org
2011-04-28 15:35 ` rguenth at gcc dot gnu.org
2011-06-03 22:20 ` ramana at gcc dot gnu.org
2012-07-02 10:37 ` rguenth at gcc dot gnu.org
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=20100723145229.8483.qmail@sourceware.org \
--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).