public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/114662] [14 regression] new test case c_lto_pr113359-2 from r14-9841-g1e3312a25a7b34 fails Date: Wed, 10 Apr 2024 05:56:45 +0000 [thread overview] Message-ID: <bug-114662-4-3Yz6daWvHh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114662-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114662 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org CC| |linkw at gcc dot gnu.org Last reconfirmed| |2024-04-10 Status|UNCONFIRMED |ASSIGNED --- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> --- I think this is a test issue, with -m32 unsigned long is 4 bytes while CL1,CL2 are 8 bytes constants, then it considers some checks would always fail and the abort will happen, since the optimization aggressively optimize away the call to getb, there is no chance to further check "semantic equality". The IR for main at *.015t.cfg looks like: int main (int argc, char * * argv) { struct SB b; struct SA a; int D.3983; <bb 2> : init (); geta (&a, &ga); _1 = a.ax; if (_1 != 3735928559) goto <bb 3>; [INV] else goto <bb 4>; [INV] <bb 3> : __builtin_abort (); <bb 4> : __builtin_abort (); }
next prev parent reply other threads:[~2024-04-10 5:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-09 18:22 [Bug lto/114662] New: " seurer at gcc dot gnu.org 2024-04-09 18:54 ` [Bug lto/114662] " ewlu at rivosinc dot com 2024-04-10 5:56 ` linkw at gcc dot gnu.org [this message] 2024-04-10 6:26 ` [Bug testsuite/114662] " linkw at gcc dot gnu.org 2024-04-10 8:01 ` cvs-commit at gcc dot gnu.org 2024-04-10 8:04 ` linkw at gcc dot gnu.org 2024-04-10 9:24 ` jamborm at gcc dot gnu.org 2024-05-21 15:47 ` 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-114662-4-3Yz6daWvHh@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).