public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/103838] New: [11/12 Regression] '-fcompare-debug' failure (length) w/ -O2 --param max-early-inliner-iterations=0 --param max-inline-insns-auto=2 Date: Sun, 26 Dec 2021 17:12:57 +0000 [thread overview] Message-ID: <bug-103838-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103838 Bug ID: 103838 Summary: [11/12 Regression] '-fcompare-debug' failure (length) w/ -O2 --param max-early-inliner-iterations=0 --param max-inline-insns-auto=2 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: debug Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- Target: x86_64-unknown-linux-gnu Created attachment 52063 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52063&action=edit diff -u uarspwmr.*.gkd gcc 12.0.0 20211219 snapshot (g:fcbf94a5be9e0c1ecad92da773a6632b86b7f70a) fails -fcompare-debug check when compiling the following testcase w/ -O2 --param max-early-inliner-iterations=0 --param max-inline-insns-auto=2: __int128 m; int n; void bar (void) { n += !!m; } void foo (void) { int i; for (i = 0; i < 2; ++i) { bar (); m /= 3; } } % x86_64-unknown-linux-gnu-gcc-12.0.0 -O2 -fcompare-debug --param max-early-inliner-iterations=0 --param max-inline-insns-auto=2 -c uarspwmr.c x86_64-unknown-linux-gnu-gcc-12.0.0: error: uarspwmr.c: '-fcompare-debug' failure (length) Diff between two gkd files attached.
next reply other threads:[~2021-12-26 17:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-26 17:12 asolokha at gmx dot com [this message] 2021-12-26 21:09 ` [Bug debug/103838] " pinskia at gcc dot gnu.org 2021-12-27 9:34 ` jakub at gcc dot gnu.org 2021-12-27 10:00 ` jakub at gcc dot gnu.org 2021-12-27 10:12 ` jakub at gcc dot gnu.org 2021-12-28 16:39 ` cvs-commit at gcc dot gnu.org 2021-12-28 16:42 ` [Bug debug/103838] [11 " jakub at gcc dot gnu.org 2022-01-24 9:20 ` cvs-commit at gcc dot gnu.org 2022-01-24 9:30 ` jakub 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-103838-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).