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/100786] [9/10/11/12 Regression] ICE: in fold_convert_loc with alias attribute and different types and different sizes
Date: Thu, 20 Jan 2022 15:50:58 +0000 [thread overview]
Message-ID: <bug-100786-4-IIRbh2GCDj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100786-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100786
--- Comment #4 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:5c12507f5d0bc080e4f346af99824e039236e61c
commit r12-6776-g5c12507f5d0bc080e4f346af99824e039236e61c
Author: Richard Biener <rguenther@suse.de>
Date: Thu Jan 20 14:25:51 2022 +0100
middle-end/100786 - constant folding from incompatible alias
The following avoids us ICEing doing constant folding from variables
with aliases of different types. The issue appears both in
folding and CCP and FRE can do more fancy stuff to still constant
fold cases where the load is smaller than the initializer so
defer it to there.
2022-01-20 Richard Biener <rguenther@suse.de>
PR middle-end/100786
* gimple-fold.cc (get_symbol_constant_value): Only return
values of compatible type to the symbol.
* gcc.dg/torture/pr100786.c: New testcase.
next prev parent reply other threads:[~2022-01-20 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 1:28 [Bug c/100786] New: ICE: in fold_convert_loc, at fold-const.c:2429 cnsun at uwaterloo dot ca
2021-05-27 3:19 ` [Bug middle-end/100786] ICE: in fold_convert_loc with alias attribute and different types and different sizes pinskia at gcc dot gnu.org
2021-12-10 2:52 ` [Bug middle-end/100786] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-20 13:29 ` rguenth at gcc dot gnu.org
2022-01-20 15:50 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-20 15:51 ` [Bug middle-end/100786] [9/10/11 " rguenth at gcc dot gnu.org
2022-02-17 9:06 ` cvs-commit at gcc dot gnu.org
2022-04-21 12:52 ` [Bug middle-end/100786] [9/10 " cvs-commit at gcc dot gnu.org
2022-05-06 11:08 ` [Bug middle-end/100786] [9 " cvs-commit at gcc dot gnu.org
2022-05-06 11:11 ` 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-100786-4-IIRbh2GCDj@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).