public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "i at maskray dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/77882] [Aarch64] Add 'naked' function attribute
Date: Wed, 25 May 2022 06:39:40 +0000 [thread overview]
Message-ID: <bug-77882-4-8eIxFh4xmo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-77882-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77882
Fangrui Song <i at maskray dot me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |i at maskray dot me
--- Comment #11 from Fangrui Song <i at maskray dot me> ---
The number of targets supporting this attribute is large but the popular
aarch64 somehow doesn't support it... I just run into a case where supporting
this would be nice (https://reviews.llvm.org/D126343#3536318).
% grep 'naked.*function attribute,' gcc/doc/extend.texi
@cindex @code{naked} function attribute, ARC
@cindex @code{naked} function attribute, ARM
@cindex @code{naked} function attribute, AVR
@cindex @code{naked} function attribute, C-SKY
@cindex @code{naked} function attribute, MCORE
@cindex @code{naked} function attribute, MSP430
@cindex @code{naked} function attribute, NDS32
@cindex @code{naked} function attribute, RISC-V
@cindex @code{naked} function attribute, RL78
@cindex @code{naked} function attribute, RX
@cindex @code{naked} function attribute, x86
next parent reply other threads:[~2022-05-25 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-77882-4@http.gcc.gnu.org/bugzilla/>
2022-05-25 6:39 ` i at maskray dot me [this message]
2022-05-25 6:45 ` pinskia at gcc dot gnu.org
2023-01-17 15:28 ` stefan.tauner at gmx dot at
2024-04-08 18:39 ` ndesaulniers at google dot com
2024-04-08 19:25 ` pinskia 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=bug-77882-4-8eIxFh4xmo@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).