public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/101254] [12 Regression] gcc head does not comply fully to -fwrapv since r12-1723
Date: Tue, 29 Jun 2021 17:38:13 +0000	[thread overview]
Message-ID: <bug-101254-4-iDfI31SqeK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101254-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101254

--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Comment on attachment 51084
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51084
another patch

Except for some consistency (max is in comments lowercase, but MIN is
uppercase), it looks good to me.
Slightly OT, wonder if something tries to handle even the swapped arguments,
i.e. relation op1 < op2 and subtraction op2 - op1.  But that can be done
incrementally if not done yet...

  parent reply	other threads:[~2021-06-29 17:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-29  9:19 [Bug c/101254] New: gcc head does not comply fully to -fwrapv bugzilla.gnu at coelho dot net
2021-06-29  9:34 ` [Bug tree-optimization/101254] [12 Regression] gcc head does not comply fully to -fwrapv since r12-1723 jakub at gcc dot gnu.org
2021-06-29 12:07 ` rguenth at gcc dot gnu.org
2021-06-29 15:09 ` amacleod at redhat dot com
2021-06-29 15:21 ` jakub at gcc dot gnu.org
2021-06-29 15:25 ` jakub at gcc dot gnu.org
2021-06-29 15:42 ` amacleod at redhat dot com
2021-06-29 15:47 ` jakub at gcc dot gnu.org
2021-06-29 15:48 ` jakub at gcc dot gnu.org
2021-06-29 15:55 ` amacleod at redhat dot com
2021-06-29 17:11 ` amacleod at redhat dot com
2021-06-29 17:38 ` jakub at gcc dot gnu.org [this message]
2021-06-29 18:27 ` amacleod at redhat dot com
2021-06-29 19:09 ` cvs-commit at gcc dot gnu.org
2021-06-29 19:10 ` amacleod at redhat dot com

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-101254-4-iDfI31SqeK@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).