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/96133] [10/11 Regression] x86-64 gcc 10.1 using -O3 leads to wrong calculation since r10-1882-g831e688af50c5f77
Date: Fri, 10 Jul 2020 08:53:07 +0000 [thread overview]
Message-ID: <bug-96133-4-XF6vStXZpS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96133-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96133
--- Comment #9 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:6e41c27bf549d957eb399d39d7d0c213f8733351
commit r11-1981-g6e41c27bf549d957eb399d39d7d0c213f8733351
Author: Richard Biener <rguenther@suse.de>
Date: Thu Jul 9 16:03:45 2020 +0200
fix constant folding from array CTORs
This fixes the case where we try to fold a read from an
array initalizer and happen to cross the boundary of
multiple CTORs which isn't really supported. For the
interesting cases like the testcase we actually handle
the folding by encoding the whole initializer.
2020-07-10 Richard Biener <rguenther@suse.de>
PR tree-optimization/96133
* gimple-fold.c (fold_array_ctor_reference): Do not
recurse to folding a CTOR that does not fully cover the
asked for object.
* gcc.dg/torture/pr96133.c: New testcase.
next prev parent reply other threads:[~2020-07-10 8:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 11:38 [Bug c++/96133] New: x86-64 gcc 10.1 using -O3 leads to wrong calculation heckflosse67 at gmx dot de
2020-07-09 12:01 ` [Bug c++/96133] [10/11 Regression] x86-64 gcc 10.1 using -O3 leads to wrong calculation since r10-1882-g831e688af50c5f77 marxin at gcc dot gnu.org
2020-07-09 12:06 ` rguenth at gcc dot gnu.org
2020-07-09 12:06 ` [Bug tree-optimization/96133] " rguenth at gcc dot gnu.org
2020-07-09 12:13 ` rguenth at gcc dot gnu.org
2020-07-09 12:18 ` rguenth at gcc dot gnu.org
2020-07-09 17:54 ` cvs-commit at gcc dot gnu.org
2020-07-09 17:55 ` rguenth at gcc dot gnu.org
2020-07-09 19:33 ` heckflosse67 at gmx dot de
2020-07-10 7:30 ` rguenth at gcc dot gnu.org
2020-07-10 8:53 ` cvs-commit at gcc dot gnu.org [this message]
2020-07-10 10:38 ` [Bug tree-optimization/96133] [10 " cvs-commit at gcc dot gnu.org
2020-07-10 10:38 ` rguenth at gcc dot gnu.org
2020-07-10 11:36 ` heckflosse67 at gmx dot de
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-96133-4-XF6vStXZpS@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).