public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug d/101127] d: Compile-time reflection for supported built-ins Date: Fri, 18 Jun 2021 17:41:50 +0000 [thread overview] Message-ID: <bug-101127-4-CdE6utqes2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-101127-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101127 --- Comment #1 from Iain Buclaw <ibuclaw at gdcproject dot org> --- There's the language hook LANG_HOOKS_BUILTIN_FUNCTION_EXT_SCOPE, which seems to do what we want on the surface, but then there's a question over whether this is to be correct. --- // static condition is false static if (__traits(compiles, __builtin_ia32_pmulhrsw128)) pragma(msg, "Yes SSSE3 support"); else { short8 truc(short8 a, short8 b) @target("ssse3") // adds SSSE3 built-ins. { return __builtin_ia32_pmulhrsw128(a, b); } } // static condition could be true, depending on order of evaluation. static if (__traits(compiles, __builtin_ia32_pmaddubsw128)) pragma(msg, "Yes SSSE3 support");
next prev parent reply other threads:[~2021-06-18 17:41 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-18 15:51 [Bug d/101127] New: " ibuclaw at gdcproject dot org 2021-06-18 17:41 ` ibuclaw at gdcproject dot org [this message] 2021-07-28 11:18 ` [Bug d/101127] " cvs-commit at gcc dot gnu.org 2021-07-28 11:36 ` cvs-commit at gcc dot gnu.org 2021-07-28 11:50 ` cvs-commit at gcc dot gnu.org 2021-07-28 11:57 ` cvs-commit at gcc dot gnu.org 2021-07-28 12:47 ` ibuclaw at gdcproject dot 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-101127-4-CdE6utqes2@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).