public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105558] simple 8-bit integer calculation fails with -O3 / march=core-avx2 on some gfortran 8/9/10 versions Date: Fri, 07 Jul 2023 10:00:53 +0000 [thread overview] Message-ID: <bug-105558-4-YZObcUKXYF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105558-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105558 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[10 Regression] simple |simple 8-bit integer |8-bit integer calculation |calculation fails with -O3 |fails with -O3 / |/ march=core-avx2 on some |march=core-avx2 on some |gfortran 8/9/10 versions |gfortran 8/9/10 versions | Known to fail| |10.5.0 Target Milestone|10.5 |--- --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- We don't know the failure mode and the identified fix isn't likely the fix. Leaving open as non-regression.
next prev parent reply other threads:[~2023-07-07 10:00 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-11 7:05 [Bug fortran/105558] New: simple 8-byte " federico.perini at gmail dot com 2022-05-11 7:51 ` [Bug fortran/105558] simple 8-bit " rguenth at gcc dot gnu.org 2022-05-11 8:15 ` federico.perini at gmail dot com 2022-05-11 8:17 ` federico.perini at gmail dot com 2022-07-15 10:45 ` marxin at gcc dot gnu.org 2022-10-27 4:57 ` [Bug tree-optimization/105558] " pinskia at gcc dot gnu.org 2022-10-27 4:58 ` [Bug tree-optimization/105558] [10 Regression] " pinskia at gcc dot gnu.org 2023-07-07 10:00 ` rguenth at gcc dot gnu.org [this message] 2023-11-07 6:19 ` [Bug tree-optimization/105558] " tkoenig 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-105558-4-YZObcUKXYF@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).