public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "akobets at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/25967] Add attribute naked for x86
Date: Tue, 05 Feb 2013 12:51:00 -0000 [thread overview]
Message-ID: <bug-25967-4-oJNiodP1GS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-25967-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25967
--- Comment #10 from Alexander Kobets <akobets at mail dot ru> 2013-02-05 12:51:00 UTC ---
(In reply to comment #1)
> A quick question here. Why not use a .s file instead?
Quick answer. CC optimizes code better, especialy for instruction sheduling.
next prev parent reply other threads:[~2013-02-05 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-25967-4@http.gcc.gnu.org/bugzilla/>
2011-12-25 17:19 ` radoslaw.biernacki at gmail dot com
2011-12-25 17:20 ` pinskia at gcc dot gnu.org
2011-12-25 21:51 ` pinskia at gcc dot gnu.org
2011-12-25 21:53 ` radoslaw.biernacki at gmail dot com
2012-03-21 0:33 ` pinskia at gcc dot gnu.org
2012-03-23 11:34 ` bryan.odonoghue at linux dot intel.com
2013-02-04 23:05 ` pinskia at gcc dot gnu.org
2013-02-05 12:51 ` akobets at mail dot ru [this message]
2006-01-26 8:00 [Bug inline-asm/25967] New: Enable " daanonym2 at hotmail dot com
2006-09-26 4:31 ` [Bug target/25967] Add " acahalan at gmail 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-25967-4-oJNiodP1GS@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).