From: nick <xerofoify@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [PATCH] Proposed patch to fix bug id, 89796 on bugzilla
Date: Mon, 25 Mar 2019 13:26:00 -0000 [thread overview]
Message-ID: <73b65dea-4bdf-d0a2-44b3-7ae5b41e4ff8@gmail.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2019-03-25 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 12:39 Nicholas Krause
2019-03-25 13:25 ` Jonathan Wakely
2019-03-25 13:26 ` nick [this message]
2019-03-25 13:30 ` Jonathan Wakely
2019-03-25 13:36 ` nick
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=73b65dea-4bdf-d0a2-44b3-7ae5b41e4ff8@gmail.com \
--to=xerofoify@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely.gcc@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).