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 target/111048] New: [14 Regression] Wrong AVX2 code on highway-1.0.6 on -O2 and above Date: Thu, 17 Aug 2023 11:40:27 +0000 [thread overview] Message-ID: <bug-111048-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111048 Bug ID: 111048 Summary: [14 Regression] Wrong AVX2 code on highway-1.0.6 on -O2 and above Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: slyfox at gcc dot gnu.org Target Milestone: --- Noticed wrong code with r14-3259-g24f7b20bbd87eb when running tests on highway-1.0.6. Extracted example: // $ cat bug.cc.cc typedef unsigned char u8; __attribute__((noipa)) static void check(const u8 * v) { if (*v != 15) __builtin_trap(); } __attribute__((noipa)) static void bug(void) { u8 in_lanes[32]; for (unsigned i = 0; i < 32; i += 2) { in_lanes[i + 0] = 0; in_lanes[i + 1] = ((u8)0xff) >> (i & 7); } check(&in_lanes[13]); } int main() { bug(); } Triggering: $ g++ bug.cc.cc -mavx2 -O2 -o bug2 && ./bug2 Illegal $ g++ bug.cc.cc -mavx2 -O1 -o bug1 && ./bug1 <ok> $ g++ -v Using built-in specs. COLLECT_GCC=/<<NIX>>/gcc-14.0.0/bin/g++ COLLECT_LTO_WRAPPER=/<<NIX>>/gcc-14.0.0/libexec/gcc/x86_64-unknown-linux-gnu/14.0.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: ../source/configure --prefix=/<<NIX>>/gcc-14.0.0 --with-gmp-include=/<<NIX>>/gmp-6.3.0-dev/include --with-gmp-lib=/<<NIX>>/gmp-6.3.0/lib --with-mpfr-include=/<<NIX>>/mpfr-4.2.0-12-dev/include --with-mpfr-lib=/<<NIX>>/mpfr-4.2.0-12/lib --with-mpc=/<<NIX>>/libmpc-1.3.1 --with-native-system-header-dir=/<<NIX>>/glibc-2.38-dev/include --with-build-sysroot=/ --program-prefix= --enable-lto --disable-libstdcxx-pch --without-included-gettext --with-system-zlib --enable-checking=release --enable-static --enable-languages=c,c++ --disable-multilib --enable-plugin --disable-libcc1 --with-isl=/<<NIX>>/isl-0.20 --disable-bootstrap --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=x86_64-unknown-linux-gnu Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.0 99999999 (experimental) (GCC)
next reply other threads:[~2023-08-17 11:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-17 11:40 slyfox at gcc dot gnu.org [this message] 2023-08-17 12:35 ` [Bug target/111048] " slyfox at gcc dot gnu.org 2023-08-17 18:32 ` [Bug middle-end/111048] " pinskia at gcc dot gnu.org 2023-08-17 18:39 ` [Bug tree-optimization/111048] " pinskia at gcc dot gnu.org 2023-08-18 7:39 ` rguenth at gcc dot gnu.org 2023-08-18 8:24 ` cvs-commit at gcc dot gnu.org 2023-08-18 8:25 ` rguenth at gcc dot gnu.org 2023-08-18 9:08 ` prathamesh3492 at gcc dot gnu.org 2023-08-18 9:35 ` rsandifo at gcc dot gnu.org 2023-08-18 14:27 ` [Bug tree-optimization/111048] [14 Regression] Wrong AVX2 code on highway-1.0.6 on -O2 and above since r14-3243-ga7dba4a1c05a76 prathamesh3492 at gcc dot gnu.org 2023-08-21 9:57 ` cvs-commit at gcc dot gnu.org 2023-08-21 11:04 ` prathamesh3492 at gcc dot gnu.org 2023-08-21 17:49 ` slyfox 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-111048-4@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).