This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla

From: nick <xerofoify at gmail dot com>
To: Jonathan Wakely <jwakely dot gcc at gmail dot com>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Mon, 25 Mar 2019 09:26:24 -0400
Subject: Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla
References: <20190325123852.2331-1-xerofoify@gmail.com> <CAH6eHdSRdUsn82mewHjS7WtOkP+4U6ZByu1w+WLpPFfemFTOuQ@mail.gmail.com>


On 2019-03-25 9:25 a.m., Jonathan Wakely wrote:
> On Mon, 25 Mar 2019 at 12:39, Nicholas Krause <xerofoify@gmail.com> wrote:
>>
>> Not sure if this is a correct fix to this bug found here:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89796 but
>> comments are welcome. If a backtrace is required please
>> let me know. I am just sending it to the development list
>> for review to make sure it's OK in terms of my understanding
>> the code.
> 
> That's what the gcc-patches list is for.
> 

Sorry it was sent there too. Didn't know which list was the correct one for
reviewing RFC patches.

Nick

Follow-Ups:
- Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla
  - From: Jonathan Wakely

References:
- [PATCH] Proposed patch to fix bug id, 89796 on bugzilla
  - From: Nicholas Krause
- Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]