public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98302] New: [11 Regression] Wrong code on aarch64 Date: Tue, 15 Dec 2020 21:15:12 +0000 [thread overview] Message-ID: <bug-98302-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98302 Bug ID: 98302 Summary: [11 Regression] Wrong code on aarch64 Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: marxin at gcc dot gnu.org CC: rsandifo at gcc dot gnu.org Target Milestone: --- Host: aarch64-linux-gnu Target: aarch64-linux-gnu Started with a costing model change, and I can reproduce it only on aarch64. The test-case is hard to reduce and comes from yarpgen: $ g++ -O3 func.ii -c $ g++ driver.ii -c $ g++ *.o $ ./a.out a.out: driver.cpp:1143: void checksum(): Assertion `var_135 == (unsigned char)0' failed. Aborted (core dumped) It's caused by vect_loop, and g++ -O3 func.ii -c -fdbg-cnt=vect_loop:1 is first value that causes that.
next reply other threads:[~2020-12-15 21:15 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-15 21:15 marxin at gcc dot gnu.org [this message] 2020-12-15 21:15 ` [Bug target/98302] " marxin at gcc dot gnu.org 2020-12-15 21:15 ` marxin at gcc dot gnu.org 2020-12-16 11:59 ` acoplan at gcc dot gnu.org 2020-12-16 12:05 ` marxin at gcc dot gnu.org 2020-12-16 12:16 ` acoplan at gcc dot gnu.org 2020-12-16 12:20 ` marxin at gcc dot gnu.org 2020-12-16 12:23 ` acoplan at gcc dot gnu.org 2020-12-16 12:57 ` marxin at gcc dot gnu.org 2020-12-16 12:58 ` marxin at gcc dot gnu.org 2020-12-16 17:08 ` acoplan at gcc dot gnu.org 2020-12-16 19:04 ` marxin at gcc dot gnu.org 2020-12-30 18:23 ` rsandifo at gcc dot gnu.org 2020-12-31 16:52 ` cvs-commit at gcc dot gnu.org 2020-12-31 16:57 ` [Bug target/98302] [?? " rsandifo at gcc dot gnu.org 2021-01-04 12:04 ` acoplan at gcc dot gnu.org 2021-01-04 15:24 ` [Bug target/98302] [9/10 " rguenth at gcc dot gnu.org 2021-01-05 9:43 ` marxin at gcc dot gnu.org 2021-01-12 10:03 ` [Bug target/98302] [9 " rsandifo at gcc dot gnu.org 2021-04-25 13:51 ` cvs-commit at gcc dot gnu.org 2021-04-25 13:53 ` rsandifo 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-98302-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).