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 middle-end/100843] [12 Regression] ICE with -O1: in try_store_by_multiple_pieces, at builtins.c:6739 since r12-397-gda9e6e63d1ae22e530ec7baf59f6ed028bf05776
Date: Wed, 15 Dec 2021 05:25:56 +0000	[thread overview]
Message-ID: <bug-100843-4-7tN2Fve2DZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100843-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexandre Oliva <aoliva@gcc.gnu.org>:

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

commit r12-5983-gc95a9f1ee7ebd461cbced455271a993bae3a42b6
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Wed Dec 15 02:22:33 2021 -0300

    [PR100843] store by mult pieces: punt on max_len < min_len

    The testcase confuses the code that detects min and max len for the
    memset, so max_len ends up less than min_len.  That shouldn't be
    possible, but the testcase requires us to handle this case.

    The store-by-mult-pieces algorithm actually relies on min and max
    lengths, so if we find them to be inconsistent, the best we can do is
    punting.


    for  gcc/ChangeLog

            PR middle-end/100843
            * builtins.c (try_store_by_multiple_pieces): Fail if min_len
            is greater than max_len.

    for  gcc/testsuite/ChangeLog

            PR middle-end/100843
            * gcc.dg/pr100843.c: New.

  parent reply	other threads:[~2021-12-15  5:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  4:04 [Bug c/100843] New: ICE with -O1: in try_store_by_multiple_pieces, at builtins.c:6739 cnsun at uwaterloo dot ca
2021-06-01  6:33 ` [Bug middle-end/100843] [12 Regression] " rguenth at gcc dot gnu.org
2021-06-01  7:14 ` [Bug middle-end/100843] [12 Regression] ICE with -O1: in try_store_by_multiple_pieces, at builtins.c:6739 since r12-397-gda9e6e63d1ae22e530ec7baf59f6ed028bf05776 marxin at gcc dot gnu.org
2021-11-19 13:13 ` aoliva at gcc dot gnu.org
2021-12-09  5:07 ` aoliva at gcc dot gnu.org
2021-12-15  5:25 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-15  5:27 ` aoliva 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-100843-4-7tN2Fve2DZ@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).