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 debug/103742] [12 Regression] '-fcompare-debug' failure (length) with -O2 -fnon-call-exceptions --param=early-inlining-insns=82 since r12-5301-g045206450386bcd7
Date: Tue, 28 Dec 2021 17:22:03 +0000 [thread overview]
Message-ID: <bug-103742-4-dgQVzxCPYR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103742-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103742
--- Comment #4 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 52078 [details]
> gcc12-pr103742.patch
>
> Untested fix that fixes it in the r12-6030 tree.
Thank you for the patch. It fixes both the reduced and original unreduced
testcase when applied on r12-6030.
next prev parent reply other threads:[~2021-12-28 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 5:44 [Bug debug/103742] New: [12 Regression] '-fcompare-debug' failure (length) with -O2 -fnon-call-exceptions --param=early-inlining-insns=82 zsojka at seznam dot cz
2021-12-16 6:52 ` [Bug debug/103742] " pinskia at gcc dot gnu.org
2021-12-16 10:04 ` [Bug debug/103742] [12 Regression] '-fcompare-debug' failure (length) with -O2 -fnon-call-exceptions --param=early-inlining-insns=82 since r12-5301-g045206450386bcd7 marxin at gcc dot gnu.org
2021-12-28 15:03 ` jakub at gcc dot gnu.org
2021-12-28 16:37 ` jakub at gcc dot gnu.org
2021-12-28 17:22 ` zsojka at seznam dot cz [this message]
2021-12-29 20:47 ` cvs-commit at gcc dot gnu.org
2021-12-29 20:56 ` 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-103742-4-dgQVzxCPYR@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: link
Be 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).