public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus at oberhumer dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/95903] gcc 10: wrong code with -fwrapv
Date: Fri, 26 Jun 2020 08:35:55 +0000	[thread overview]
Message-ID: <bug-95903-4-b9TZmrh55U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95903-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Markus F.X.J. Oberhumer <markus at oberhumer dot com> ---
Yes, ilp32 might be a corner case.

Still, clang-10 does create the expected code.

See https://gcc.godbolt.org/z/aEokbX for

  clang-10 -target arm64_32-ios -O2 -fomit-frame-pointer -fwrapv

and 

  clang-10 -target arm64_32-ios -O2 -fomit-frame-pointer -fno-wrapv

  parent reply	other threads:[~2020-06-26  8:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 23:25 [Bug middle-end/95903] New: " markus at oberhumer dot com
2020-06-26  6:30 ` [Bug middle-end/95903] " jakub at gcc dot gnu.org
2020-06-26  7:41 ` markus at oberhumer dot com
2020-06-26  8:05 ` jakub at gcc dot gnu.org
2020-06-26  8:35 ` markus at oberhumer dot com [this message]
2020-06-26  8:56 ` jakub at gcc dot gnu.org
2020-06-26 10:38 ` markus at oberhumer dot com
2020-06-26 11:03 ` jakub at gcc dot gnu.org
2020-06-26 11:17 ` markus at oberhumer dot com
2020-06-26 11:36 ` markus at oberhumer dot com
2020-06-27 10:42 ` cvs-commit at gcc dot gnu.org
2020-06-29  9:35 ` cvs-commit at gcc dot gnu.org
2020-09-16 19:22 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:55 ` 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-95903-4-b9TZmrh55U@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).