From: Marek Polacek <polacek@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [ubsan PATCH] Fix compile-time hog with &TARGET_EXPRs (PR sanitizer/70342)
Date: Fri, 29 Apr 2016 12:35:00 -0000 [thread overview]
Message-ID: <20160429123525.GB5348@redhat.com> (raw)
In-Reply-To: <20160428141541.GQ26501@tucnak.zalov.cz>
On Thu, Apr 28, 2016 at 04:15:41PM +0200, Jakub Jelinek wrote:
> On Thu, Apr 28, 2016 at 04:10:01PM +0200, Marek Polacek wrote:
> > That works too, though it of course affects all users, not just ubsan. Here's
>
> Of course, but I think that is a good thing ;)
>
> > the patch with your suggested change.
> >
> > Bootstrapped/regtested on x86_64-linux, ok for trunk?
> >
> > 2016-04-28 Marek Polacek <polacek@redhat.com>
> > Jakub Jelinek <jakub@redhat.com>
> >
> > PR sanitizer/70342
> > * fold-const.c (tree_single_nonzero_warnv_p): For TARGET_EXPR, use
> > TARGET_EXPR_SLOT as a base.
> >
> > * g++.dg/ubsan/null-7.C: New test.
>
> Ok for trunk.
Thanks, committed.
> For 6.2 dunno, either the same patch after a while, or perhaps your original
> patch is safer (though, wonder if e.g. one can construct a testcase where it
> will use instrument &(TARGET_EXPR <...>.field) nested many times and still
> trigger the compile time hog with your patch).
Dunno either. I think I'll backport the same patch after a week or so.
Marek
prev parent reply other threads:[~2016-04-29 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 17:03 Marek Polacek
2016-04-28 9:07 ` Jakub Jelinek
2016-04-28 14:10 ` Marek Polacek
2016-04-28 14:15 ` Jakub Jelinek
2016-04-29 12:35 ` Marek Polacek [this message]
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=20160429123525.GB5348@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).