public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108734] powerpc: False Detection of __atomic_*_8 Builtins Date: Thu, 09 Feb 2023 17:56:48 +0000 [thread overview] Message-ID: <bug-108734-4-gpBvtsHdh0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108734-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108734 David Edelsohn <dje at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dje at gcc dot gnu.org --- Comment #5 from David Edelsohn <dje at gcc dot gnu.org> --- Rohan, I'm sorry that this is confusing, but the issue is cockpit error. __has_builtin() does not mean that the builtin is inlined. It only means that GCC recognizes the builtin. That is how __has_builtin() is documented. In 32 bit mode, GCC emits an external reference for the builtin: 8 byte atomic requires libatomic library, which is not linked by default (and shouldn't be).
next prev parent reply other threads:[~2023-02-09 17:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-09 3:53 [Bug c/108734] New: " rmclure at linux dot ibm.com 2023-02-09 3:56 ` [Bug c/108734] " pinskia at gcc dot gnu.org 2023-02-09 3:59 ` rmclure at linux dot ibm.com 2023-02-09 7:56 ` pinskia at gcc dot gnu.org 2023-02-09 8:19 ` redi at gcc dot gnu.org 2023-02-09 17:56 ` dje at gcc dot gnu.org [this message] 2023-02-09 23:40 ` rmclure at linux dot ibm.com 2023-02-10 9:33 ` redi 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-108734-4-gpBvtsHdh0@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).