public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44290] [4.5 Regression] arm linux kernel crahes when built with -fipa-sra, __naked attribute is broken
Date: Sat, 29 May 2010 14:40:00 -0000 [thread overview]
Message-ID: <20100529143948.22960.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44290-10179@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from mikpe at it dot uu dot se 2010-05-29 14:39 -------
(In reply to comment #11)
> (it seems quite stupid to have naked functions with only an asm inside in the
> first place - you can equally well use plain assembly)
Except that with plain asm() for an entire function definition you'd also have
to include boring preamble/postamble stuff like .align/.type/.size if you want
it to appear as a proper function, and you still have to declarate a prototype.
And the reason for making it a separate function rather than an inline asm() is
probably related to register assignment: a separate function can (could) make
assumptions about parameter registers and scratch registers. With inline asm()
you have to be much more elaborate, esp. if you have constraints that gcc
cannot express, like even/odd register pairs on ARM.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44290
next prev parent reply other threads:[~2010-05-29 14:40 UTC|newest]
Thread overview: 30+ 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 [this message]
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
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
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=20100529143948.22960.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).