public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/103788] [9/10/11/12 Regression] '-fcompare-debug' failure (length) w/ -O1
Date: Tue, 21 Dec 2021 18:51:23 +0000 [thread overview]
Message-ID: <bug-103788-4-KXBsOMtUBC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103788-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103788
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> (In reply to Martin Liška from comment #1)
> > Likely latent which was exposed with r9-3352-g87bd153645f393a1.
here is a slightly modified (just line rather than column change) which fails
in GCC 8 also:
int
bar (void);
int
foo (int x)
{
int i;
for (i = 0; i <= __INT_MAX__; ++i)
x += bar () < (
x ? 2 : 1 );
return x;
}
next prev parent reply other threads:[~2021-12-21 18:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 12:01 [Bug debug/103788] New: " asolokha at gmx dot com
2021-12-21 13:57 ` [Bug debug/103788] " marxin at gcc dot gnu.org
2021-12-21 18:44 ` pinskia at gcc dot gnu.org
2021-12-21 18:46 ` pinskia at gcc dot gnu.org
2021-12-21 18:51 ` pinskia at gcc dot gnu.org [this message]
2021-12-21 19:00 ` pinskia at gcc dot gnu.org
2021-12-22 4:38 ` asolokha at gmx dot com
2021-12-22 8:42 ` marxin at gcc dot gnu.org
2022-01-18 13:58 ` rguenth at gcc dot gnu.org
2022-01-28 12:23 ` jakub at gcc dot gnu.org
2022-05-27 9:46 ` [Bug debug/103788] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:47 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug debug/103788] [11/12/13/14 " rguenth 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-103788-4-KXBsOMtUBC@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).