public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/115403] [15 Regression] highway build from git fails with 'target specific option mismatch' since r15-902-geff00046409a72 Date: Sun, 09 Jun 2024 08:59:33 +0000 [thread overview] Message-ID: <bug-115403-4-BcKEp7c8EE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115403-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115403 --- Comment #1 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- Created attachment 58388 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58388&action=edit float_test.cc.cc.xz Attaching preprocessed file. It fails as: $ g++ -O2 -std=c++17 -c float_test.cc.cc float_test.cc.cc: In function 'constexpr bool hwy::ScalarIsInf(T) [with T = float16_t]': float_test.cc.cc:15617:108: error: inlining failed in call to 'always_inline' 'constexpr To hwy::BitCastScalar(const From&) [with To = short unsigned int; From = float16_t; EnableIf<((bool)(! IsSpecialFloat<To>()))>* <anonymous> = 0]': target specific option mismatch 15617 | ine)) __attribute__((flatten)) __attribute__((unused)) constexpr To BitCastScalar(const From& val) { | ^~~~~~~~~~~~~ float_test.cc.cc:16478:43: note: called from here 16478 | return static_cast<TU>(BitCastScalar<TU>(static_cast<TF>(val)) << 1) == | ~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~
next prev parent reply other threads:[~2024-06-09 8:59 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-09 8:54 [Bug c++/115403] New: " slyfox at gcc dot gnu.org 2024-06-09 8:59 ` slyfox at gcc dot gnu.org [this message] 2024-06-09 10:17 ` [Bug c++/115403] " slyfox at gcc dot gnu.org 2024-06-09 16:46 ` [Bug c++/115403] [15 Regression] highway build from git fails with 'target specific option mismatch' (templates) " 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-115403-4-BcKEp7c8EE@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).