public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Martin Sebor <msebor@gmail.com>, Gerald Pfeifer <gerald@pfeifer.com>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix various minor gimple-ssa-sprintf.c issues
Date: Wed, 28 Sep 2016 04:43:00 -0000	[thread overview]
Message-ID: <56e6923d-6996-abec-ad11-65e925bd825f@redhat.com> (raw)
In-Reply-To: <979ef9fb-a63f-7948-6c05-f98448557694@gmail.com>

On 09/27/2016 11:29 AM, Martin Sebor wrote:
> On 09/26/2016 02:30 AM, Gerald Pfeifer wrote:
>> Hi Martin,
>>
>> I'm afraid there may be further fallout from your patch.  GCC
>> now bootstraps fine on my tester, but building Wine I started
>> to see
>>
>>   internal compiler error: in format_floating, at
>> gimple-ssa-sprintf.c:1165
>>
>> four or so days ago.
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77740 has the invocation
>> and a preprocessed input file.
>
> Thanks.  (As I just commented in pr77740, so just to close to loop
> here) a patch for the problem awaits code review:
>
>   https://gcc.gnu.org/ml/gcc-patches/2016-09/msg01470.html
I didn't see this in my folder of things to review, so sorry it lingered.

It's OK for the trunk.

THanks,
Jeff

      parent reply	other threads:[~2016-09-28  4:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-21 15:19 Jakub Jelinek
2016-09-22  4:54 ` Martin Sebor
2016-09-22  7:40   ` Jakub Jelinek
2016-09-22  8:35     ` Marek Polacek
2016-09-23 17:59       ` Martin Sebor
2016-09-22 15:29     ` Martin Sebor
2016-09-26  9:21   ` Gerald Pfeifer
2016-09-27 17:33     ` Martin Sebor
2016-09-27 17:52       ` Martin Sebor
2016-09-28  4:43       ` Jeff Law [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=56e6923d-6996-abec-ad11-65e925bd825f@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=msebor@gmail.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).