public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/108599] [12/13 Regression] Incorrect code generation newer intel architectures Date: Mon, 30 Jan 2023 13:49:38 +0000 [thread overview] Message-ID: <bug-108599-4-Z8VBiRc78c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108599 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |12.3 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Last reconfirmed| |2023-01-30 Summary|Incorrect code generation |[12/13 Regression] |newer intel architectures |Incorrect code generation |for gcc 12 and 13 |newer intel architectures CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> --- With just -O3 -march=haswell on following test it started with r13-4124-g156f523f9582f1e6bcce27ece03f2776960408c8 With -O2 -march=haswell -mtune=skylake-avx512 started with r12-4240-g2b8453c401b699ed93c085d0413ab4b5030bcdb8 Finally with -O3 -march=haswell -mtune=skylake-avx512 with r12-2666-g29f0e955c97da002b5adb4e8c9dfd2ea9709e207 __attribute__((noipa, noreturn)) void bar (const char *, const char *, unsigned int, const char *) noexcept { __builtin_abort (); } # define assert(expr) \ (static_cast <bool> (expr) \ ? void (0) \ : bar (#expr, __FILE__, __LINE__, __PRETTY_FUNCTION__)) typedef decltype (sizeof 0) size_t; struct Stats { size_t _used; size_t _hold; size_t _dead; size_t _extra_used; Stats () : _used(0), _hold(0), _dead(0), _extra_used(0) {} Stats used (size_t val) { _used += val; return *this; } Stats hold (size_t val) { _hold += val; return *this; } }; void foo (size_t exp_used, size_t exp_hold, size_t exp_dead, size_t exp_extra_used, const Stats stats) { assert (exp_used == stats._used); assert (exp_hold == stats._hold); assert (exp_dead == stats._dead); assert (exp_extra_used == stats._extra_used); } int main () { foo (16, 0, 0, 0, Stats ().used (16).hold (0)); foo (16, 16, 0, 0, Stats ().used (16).hold (16)); }
next prev parent reply other threads:[~2023-01-30 13:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-30 13:18 [Bug c++/108599] New: Incorrect code generation newer intel architectures for gcc 12 and 13 balder at yahooinc dot com 2023-01-30 13:20 ` [Bug c++/108599] " balder at yahooinc dot com 2023-01-30 13:32 ` [Bug target/108599] " balder at yahooinc dot com 2023-01-30 13:49 ` jakub at gcc dot gnu.org [this message] 2023-01-30 14:00 ` [Bug target/108599] [12/13 Regression] Incorrect code generation newer intel architectures jakub at gcc dot gnu.org 2023-01-30 14:10 ` jakub at gcc dot gnu.org 2023-01-30 14:31 ` jakub at gcc dot gnu.org 2023-01-30 15:17 ` rguenth at gcc dot gnu.org 2023-01-30 15:19 ` jakub at gcc dot gnu.org 2023-01-31 9:12 ` cvs-commit at gcc dot gnu.org 2023-01-31 9:14 ` [Bug target/108599] [12 " jakub at gcc dot gnu.org 2023-02-09 11:54 ` balder at yahooinc dot com 2023-02-09 12:02 ` jakub at gcc dot gnu.org 2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org 2023-02-10 18:01 ` jakub 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-108599-4-Z8VBiRc78c@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).