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/100278] IBM Z: Segmentation fault when building valgrind with -march=z14
Date: Tue, 27 Apr 2021 08:30:14 +0000 [thread overview]
Message-ID: <bug-100278-4-z1pPz7FIHl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100278-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100278
--- Comment #2 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:acfe5290406cc70485df8899d14982278a9371f8
commit r12-141-gacfe5290406cc70485df8899d14982278a9371f8
Author: Richard Biener <rguenther@suse.de>
Date: Tue Apr 27 09:41:38 2021 +0200
tree-optimization/100278 - handle mismatched code in TBAA adjust of PRE
PRE has code to adjust TBAA behavior for refs that expects the base
operation code to match. The testcase shows a case where we have
a VAR_DECL vs. a MEM_REF so add code to give up in such cases.
2021-04-27 Richard Biener <rguenther@suse.de>
PR tree-optimization/100278
* tree-ssa-pre.c (compute_avail): Give up when we cannot
adjust TBAA beacuse of mismatching bases.
* gcc.dg/tree-ssa/pr100278.c: New testcase.
next prev parent reply other threads:[~2021-04-27 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 1:32 [Bug middle-end/100278] New: " iii at linux dot ibm.com
2021-04-27 7:13 ` [Bug middle-end/100278] " rguenth at gcc dot gnu.org
2021-04-27 8:30 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-27 8:32 ` rguenth at gcc dot gnu.org
2021-05-05 9:01 ` cvs-commit at gcc dot gnu.org
2021-05-05 9:42 ` cvs-commit at gcc dot gnu.org
2021-06-01 10:56 ` iii at linux dot ibm.com
2021-09-17 6:42 ` pinskia 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-100278-4-z1pPz7FIHl@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).