From: marxin <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 0/5] Fix various MPX issues
Date: Tue, 07 Mar 2017 10:09:00 -0000 [thread overview]
Message-ID: <cover.1488881229.git.mliska@suse.cz> (raw)
Hello.
I'm sending a small series that fixes MPX issue that are quite easily fixable.
The series can bootstrap on ppc64le and survives regression tests.
Thanks for review,
Martin
marxin (5):
Fix *_CST ICEs connected to MPX.
Get bounds for a PARM_DECL (PR ipa/79761).
Fix ICE in tree-chkp-opt.c (PR tree-optimization/79631).
Disable -fcheck-pointer-bounds with sanitizers.
Support BIT_FIELD_REF in MPX (PR ipa/79764).
gcc/testsuite/g++.dg/pr79761.C | 34 ++++++++++
gcc/testsuite/g++.dg/pr79764.C | 12 ++++
gcc/testsuite/g++.dg/pr79769.C | 4 ++
gcc/testsuite/gcc.target/i386/mpx/pr79631.c | 15 +++++
gcc/testsuite/gcc.target/i386/mpx/pr79763.c | 6 ++
gcc/testsuite/gcc.target/i386/mpx/pr79770.c | 20 ++++++
gcc/testsuite/gcc.target/i386/pr71458.c | 2 +-
gcc/toplev.c | 29 ++++-----
gcc/tree-chkp-opt.c | 3 +-
gcc/tree-chkp.c | 96 +++++++++++++++++++++++------
10 files changed, 184 insertions(+), 37 deletions(-)
create mode 100644 gcc/testsuite/g++.dg/pr79761.C
create mode 100644 gcc/testsuite/g++.dg/pr79764.C
create mode 100644 gcc/testsuite/g++.dg/pr79769.C
create mode 100644 gcc/testsuite/gcc.target/i386/mpx/pr79631.c
create mode 100644 gcc/testsuite/gcc.target/i386/mpx/pr79763.c
create mode 100644 gcc/testsuite/gcc.target/i386/mpx/pr79770.c
--
2.11.1
next reply other threads:[~2017-03-07 10:09 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 10:09 marxin [this message]
2017-03-07 10:09 ` [PATCH 2/5] Get bounds for a PARM_DECL (PR ipa/79761) marxin
2017-03-07 10:16 ` Rainer Orth
2017-03-07 14:48 ` Martin Liška
2017-03-07 14:57 ` Richard Biener
2017-03-07 16:07 ` Martin Liška
2017-03-07 16:17 ` Jeff Law
2017-03-08 11:01 ` Richard Biener
2017-03-07 10:09 ` [PATCH 3/5] Fix ICE in tree-chkp-opt.c (PR tree-optimization/79631) marxin
2017-03-09 9:36 ` Martin Liška
2017-03-09 10:05 ` Richard Biener
2017-03-09 10:12 ` Martin Liška
2017-03-07 10:09 ` [PATCH 5/5] Support BIT_FIELD_REF in MPX (PR ipa/79764) marxin
2017-03-07 10:18 ` Rainer Orth
2017-03-07 14:49 ` Martin Liška
2017-03-07 15:00 ` Richard Biener
2017-03-07 10:09 ` [PATCH 1/5] Fix *_CST ICEs connected to MPX marxin
2017-03-07 10:17 ` Rainer Orth
2017-03-07 14:48 ` Martin Liška
2017-03-07 14:53 ` Richard Biener
2017-03-07 16:01 ` Martin Liška
2017-03-08 11:00 ` Richard Biener
2017-03-09 11:40 ` Martin Liška
2017-03-13 12:28 ` Richard Biener
2017-03-13 13:02 ` Martin Liška
2017-03-13 13:08 ` Richard Biener
2017-03-13 13:33 ` Martin Liška
2017-03-14 23:58 ` Ilya Enkovich
2017-03-15 10:12 ` Martin Liška
2017-03-15 17:09 ` Jeff Law
2017-03-07 10:09 ` [PATCH 4/5] Disable -fcheck-pointer-bounds with sanitizers marxin
2017-03-07 16:12 ` Jeff Law
2017-03-07 16:21 ` Jakub Jelinek
2017-03-09 10:02 ` Martin Liška
2017-03-10 13:09 ` [PATCH] MPX: Fix option handling Martin Liška
2017-03-10 13:14 ` Jakub Jelinek
2017-03-17 12:17 ` Rainer Orth
2017-03-21 11:21 ` Martin Liška
2017-03-09 14:19 ` [PATCH 6/N] Do not warn -Wsuggest-attribute=noreturn for main.chkp (PR, middle-end/78339) Martin Liška
2017-03-13 12:29 ` Richard Biener
2017-03-07 10:26 [PATCH 0/5] Fix various MPX issues Uros Bizjak
2017-03-07 14:47 ` Martin Liška
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=cover.1488881229.git.mliska@suse.cz \
--to=mliska@suse.cz \
--cc=gcc-patches@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).