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/100509] [9/10 Regression] ICE at -O3: in fold_convert_loc with variable (attribute) alias of different types
Date: Wed, 16 Jun 2021 14:24:15 +0000	[thread overview]
Message-ID: <bug-100509-4-jrd6n7vguH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100509-4@http.gcc.gnu.org/bugzilla/>

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

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

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

commit r10-9921-gcd712310edc2ffeec8982ba5f9aeaa0b14e93cf1
Author: Richard Biener <rguenther@suse.de>
Date:   Tue May 11 10:58:35 2021 +0200

    middle-end/100509 - avoid folding constant to aggregate type

    When folding a constant initializer looking through aliases to
    incompatible types can lead to us trying to fold a constant
    to an aggregate type which can't work.  Simply avoid trying
    to constant fold non-register typed symbols.

    2021-05-11  Richard Biener  <rguenther@suse.de>

            PR middle-end/100509
            * gimple-fold.c (fold_gimple_assign): Only call
            get_symbol_constant_value on register type symbols.

            * gcc.dg/pr100509.c: New testcase.

    (cherry picked from commit ca8e8301180fa71de1a76769fc038df2ab85dfeb)

  parent reply	other threads:[~2021-06-16 14:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 19:34 [Bug c/100509] New: ICE at -O3: in fold_convert_loc, at fold-const.c:2552 cnsun at uwaterloo dot ca
2021-05-10 21:15 ` [Bug tree-optimization/100509] ICE at -O3: in fold_convert_loc with variable (attribute) alias of different types pinskia at gcc dot gnu.org
2021-05-11  7:07 ` rguenth at gcc dot gnu.org
2021-05-11  8:09 ` marxin at gcc dot gnu.org
2021-05-11 10:48 ` cvs-commit at gcc dot gnu.org
2021-05-11 10:49 ` [Bug tree-optimization/100509] [9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-05-25  8:07 ` cvs-commit at gcc dot gnu.org
2021-06-01  8:20 ` [Bug tree-optimization/100509] [9/10 " rguenth at gcc dot gnu.org
2021-06-16 14:24 ` cvs-commit at gcc dot gnu.org [this message]
2021-10-13 10:09 ` [Bug tree-optimization/100509] [9 " cvs-commit at gcc dot gnu.org
2021-10-13 10:10 ` 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-100509-4-jrd6n7vguH@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).