public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rafael_andreas at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/96628] Feature request: __attribute__((no_builtin("Foo"))) Date: Sun, 16 Aug 2020 00:18:06 +0000 [thread overview] Message-ID: <bug-96628-4-jRW4GncMTU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96628-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96628 Rafaël Kooi <rafael_andreas at hotmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rafael_andreas at hotmail dot com Summary|Feature request: |Feature request: |__attribute__((no_builtin(F |__attribute__((no_builtin(" |oo))) |Foo"))) --- Comment #1 from Rafaël Kooi <rafael_andreas at hotmail dot com> --- Clang supports __attribute__((no_builtin("memset"))) for things like implementing memset in a CRT. This is preferable over using -fno-builtin cause it disables all builtins, which is not optimal when it comes to possible optimizations. I also wasn't able to find out how to disable a specific builtin from the commandline, which could be used as a workaround by just splitting functionally up into more files. Right now my CRT project doesn't work with GCC on Windows because of reliance on this attribute, msvc ABI, and SEH support, but I would like to be able to also compile it with GCC for portability reasons and this would be a big step.
next prev parent reply other threads:[~2020-08-16 0:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-16 0:08 [Bug other/96628] New: Feature request: __attribute__((no_builtin(Foo))) rafael_andreas at hotmail dot com 2020-08-16 0:18 ` rafael_andreas at hotmail dot com [this message] 2020-08-16 7:19 ` [Bug other/96628] Feature request: __attribute__((no_builtin("Foo"))) schwab@linux-m68k.org 2020-08-16 22:43 ` rafael_andreas at hotmail dot com 2020-08-16 22:51 ` pinskia at gcc dot gnu.org 2020-08-17 0:32 ` rafael_andreas at hotmail dot com 2020-08-25 11:47 ` rsandifo at gcc dot gnu.org 2023-06-03 1:17 ` [Bug c/96628] " 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-96628-4-jRW4GncMTU@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: linkBe 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).