public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/105517] [13 Regression] Missing diagnostic after recent optimizer improvements
Date: Mon, 09 May 2022 11:42:59 +0000	[thread overview]
Message-ID: <bug-105517-4-vODHlhoeFC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105517-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:faabc751d0bb7e7fe86abfe8991b0307d585874a

commit r13-205-gfaabc751d0bb7e7fe86abfe8991b0307d585874a
Author: Richard Biener <rguenther@suse.de>
Date:   Mon May 9 11:33:44 2022 +0200

    tree-optimization/105517 - avoid offset truncation during VN

    When value-numbering an address expression like
    &p_74(D)->a1x[4294967295].a1; we are accumulating the byte offset
    in an 64bit integer.  When later exploiting the duality between
    that and a POINTER_PLUS_EXPR we should avoid truncating that
    offset to fit in the target specific sizetype.  While such
    overflows are generally undefined behavior, exploiting this
    may leads to spurious missing diagnostics.

    2022-05-09  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/105517
            * tree-ssa-sccvn.cc (vn_reference_lookup): Make sure the
accumulated
            offset can be represented in the POINTER_PLUS_EXPR IL.
            (vn_reference_insert): Likewise.
            * poly-int.h (sext_hwi): Add poly version of sext_hwi.

  parent reply	other threads:[~2022-05-09 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 15:12 [Bug tree-optimization/105517] New: " law at gcc dot gnu.org
2022-05-09  8:08 ` [Bug tree-optimization/105517] " rguenth at gcc dot gnu.org
2022-05-09  9:33 ` rguenth at gcc dot gnu.org
2022-05-09 11:42 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-09 11:46 ` 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-105517-4-vODHlhoeFC@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).