public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "th020394 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/52646] New: Clang LLVM's __attribute__((naked)) for GCC when compiling for x86
Date: Wed, 21 Mar 2012 00:33:00 -0000	[thread overview]
Message-ID: <bug-52646-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52646

             Bug #: 52646
           Summary: Clang LLVM's __attribute__((naked)) for GCC when
                    compiling for x86
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: other
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: th020394@gmail.com


It would be helpful to system developers if GCC had something similar to Clang
LLVM's __attribute__((naked)) for x86 targets. There are cases, such as when
interfacing with assembly or when handling an interrupt, when the code that
precedes and follows a normal function causes problems.

GCC already has __attribute__((interrupt)) for multiple targets, but doesn't
implement it for x86. Personally, if the feature were to be implemented, I
believe naked is more explicit.

I'd be glad to do this myself, but I'm not acquainted with GCC at all. What
files should I look in to get started?


             reply	other threads:[~2012-03-21  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21  0:33 th020394 at gmail dot com [this message]
2012-03-21  0:37 ` [Bug other/52646] " pinskia at gcc dot gnu.org
2012-03-21  0:59 ` th020394 at gmail dot com
2012-03-21  1:07 ` steven at gcc dot gnu.org
2012-03-21  1:54 ` th020394 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-52646-4@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).