public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amacleod at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/98026] optimization dependant on condition order
Date: Fri, 28 Jan 2022 23:18:04 +0000 [thread overview]
Message-ID: <bug-98026-4-579dcbTqHs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98026-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98026
--- Comment #5 from Andrew Macleod <amacleod at redhat dot com> ---
(In reply to Andrew Macleod from comment #4)
> > void f4(signed int i,unsigned int j) {
> > if (i > 100) return;
> > if (j > i) return;
> >
> > if (j > 100) link_error();
>
> if i is -2 (0xfffffffe) and j is 0xffffffffff (-1)
>
> then link error cant be removed.. ?
err, j is 0xfffffffd (-3) you get the idea :-)
Friday evenings are killer for logic and bit patterns...
prev parent reply other threads:[~2022-01-28 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 10:04 [Bug tree-optimization/98026] New: " denis.campredon at gmail dot com
2020-11-27 10:52 ` [Bug tree-optimization/98026] " rguenth at gcc dot gnu.org
2021-07-19 4:17 ` pinskia at gcc dot gnu.org
2022-01-12 19:34 ` amacleod at redhat dot com
2022-01-28 23:15 ` amacleod at redhat dot com
2022-01-28 23:18 ` amacleod at redhat dot com [this message]
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-98026-4-579dcbTqHs@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).