public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99863] New: [10/11 Regression] wrong code with -O -fno-tree-forwprop -mno-sse2 Date: Thu, 01 Apr 2021 08:44:32 +0000 [thread overview] Message-ID: <bug-99863-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99863 Bug ID: 99863 Summary: [10/11 Regression] wrong code with -O -fno-tree-forwprop -mno-sse2 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Created attachment 50493 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50493&action=edit reduced testcase Output: $ x86_64-pc-linux-gnu-gcc -O -fno-tree-forwprop -mno-sse2 testcase.c -Wno-psabi $ ./a.out Aborted $ x86_64-pc-linux-gnu-gcc -v Using built-in specs. COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-r11-7937-20210331154556-geadf009b229-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/11.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++ --enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra --with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld --with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-r11-7937-20210331154556-geadf009b229-checking-yes-rtl-df-extra-amd64 Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 11.0.1 20210331 (experimental) (GCC)
next reply other threads:[~2021-04-01 8:44 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-01 8:44 zsojka at seznam dot cz [this message] 2021-04-01 9:01 ` [Bug target/99863] " rguenth at gcc dot gnu.org 2021-04-01 9:14 ` rguenth at gcc dot gnu.org 2021-04-01 9:58 ` rguenth at gcc dot gnu.org 2021-04-01 10:02 ` [Bug target/99863] [10/11 Regression] wrong code with -O -fno-tree-forwprop -mno-sse2 since r10-7268-g529ea7d9596b26ba marxin at gcc dot gnu.org 2021-04-01 10:24 ` rguenth at gcc dot gnu.org 2021-04-01 10:45 ` [Bug rtl-optimization/99863] " rguenth at gcc dot gnu.org 2021-04-01 10:47 ` cvs-commit at gcc dot gnu.org 2021-04-01 11:16 ` ebotcazou at gcc dot gnu.org 2021-04-01 11:28 ` ebotcazou at gcc dot gnu.org 2021-04-01 12:26 ` jakub at gcc dot gnu.org 2021-04-01 12:45 ` rguenther at suse dot de 2021-04-01 13:01 ` jakub at gcc dot gnu.org 2021-04-01 13:23 ` jakub at gcc dot gnu.org 2021-04-01 13:27 ` jakub at gcc dot gnu.org 2021-04-01 13:32 ` rguenther at suse dot de 2021-04-01 13:35 ` jakub at gcc dot gnu.org 2021-04-01 13:54 ` jakub at gcc dot gnu.org 2021-04-03 8:07 ` cvs-commit at gcc dot gnu.org 2021-04-03 8:16 ` [Bug rtl-optimization/99863] [10 " jakub at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-20 9:45 ` cvs-commit at gcc dot gnu.org 2021-04-20 9:50 ` jakub at gcc dot gnu.org 2021-04-20 23:34 ` cvs-commit at gcc dot gnu.org 2021-04-22 16:52 ` cvs-commit 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-99863-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).