public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "baiwfg2 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110399] pointer substraction causes coredump with ftrapv on edge case
Date: Thu, 29 Jun 2023 09:33:37 +0000	[thread overview]
Message-ID: <bug-110399-4-Qh7UofsjZM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110399-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Chan Lewis <baiwfg2 at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> Dup of bug 13421.
> 
> *** This bug has been marked as a duplicate of bug 13421 ***

I see. I wonder why gcc consider pointer signed and need to abort in this case,
whereas clang still works as expected. If we change pointer to unsigned in our
codebase, that will be lots of work.

      parent reply	other threads:[~2023-06-29  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25  1:49 [Bug c/110399] New: " baiwfg2 at gmail dot com
2023-06-25  1:59 ` [Bug middle-end/110399] " pinskia at gcc dot gnu.org
2023-06-25  2:01 ` pinskia at gcc dot gnu.org
2023-06-29  9:33 ` baiwfg2 at gmail 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-110399-4-Qh7UofsjZM@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).