From: Richard Biener <richard.guenther@gmail.com>
To: Richard Biener <rguenther@suse.de>
Cc: "Jakub Jelinek" <jakub@redhat.com>, "Jeff Law" <law@redhat.com>,
"Martin Liška" <mliska@suse.cz>,
"GCC Patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix i?86 bootstrap (PR rtl-optimization/82044)
Date: Wed, 22 Nov 2017 09:11:00 -0000 [thread overview]
Message-ID: <CAFiYyc0D64PY9p5aCds6hxTRXe0FYB6cVtivvsOCp3=MJfaWTg@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1711220954340.12252@zhemvz.fhfr.qr>
On Wed, Nov 22, 2017 at 9:54 AM, Richard Biener <rguenther@suse.de> wrote:
> On Wed, 22 Nov 2017, Jakub Jelinek wrote:
>
>> On Wed, Nov 22, 2017 at 12:27:20AM +0100, Jakub Jelinek wrote:
>> > The following patch fixes those two issues and adds similar overflow
>> > check to record_store too (in that spot width is always non-negative, so
>> > we don't need a special width == -1 handling).
>> >
>> > Bootstrapped successfully on i686-linux, ok for trunk if it passes regtest
>> > there (and pending x86_64-linux bootstrap + regtest)?
>>
>> Now successfully bootstrapped/regtested on both.
>
> Ok.
I've reverted the patch on the branch. This isn't stuff we should
backport IMHO.
Richard.
> Richard.
next prev parent reply other threads:[~2017-11-22 9:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 7:51 [PATCH] Fix UBSAN errors in dse.c " Martin Liška
2017-09-20 8:15 ` Jakub Jelinek
2017-10-19 11:58 ` Martin Liška
2017-11-02 13:15 ` Martin Liška
2017-11-08 16:42 ` Jeff Law
2017-11-15 7:34 ` Martin Liška
2017-11-17 0:57 ` Jeff Law
2017-11-22 0:27 ` [PATCH] Fix i?86 bootstrap " Jakub Jelinek
2017-11-22 8:01 ` Jakub Jelinek
2017-11-22 9:00 ` Richard Biener
2017-11-22 9:11 ` Richard Biener [this message]
2017-12-19 11:26 ` Martin Liška
2017-11-22 9:45 ` Eric Botcazou
2017-11-22 9:52 ` Jakub Jelinek
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='CAFiYyc0D64PY9p5aCds6hxTRXe0FYB6cVtivvsOCp3=MJfaWTg@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=mliska@suse.cz \
--cc=rguenther@suse.de \
/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).