From: Jeff Law <law@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>,
Joseph Myers <joseph@codesourcery.com>,
Nathan Sidwell <nathan@acm.org>, Jason Merrill <jason@redhat.com>
Subject: Re: [PATCH] Use complete_array_type on flexible array member initializers
Date: Thu, 06 Sep 2018 22:26:00 -0000 [thread overview]
Message-ID: <a09d3de8-8e73-d86a-2194-c415988386b7@redhat.com> (raw)
In-Reply-To: <4a533150-c63c-4bfd-5bd2-8cc78b63f17e@redhat.com>
On 09/06/2018 04:16 PM, Jeff Law wrote:
> On 09/06/2018 04:01 PM, Jeff Law wrote:
>> On 09/06/2018 11:12 AM, Bernd Edlinger wrote:
>>
>>>>
>>>
>>> Ah, thanks a lot.
>>>
>>> Okay, this is the status of the STRING-CST semantic-v2 patches:
>>>
>>> [PATCH] Check the STRING_CSTs in varasm.c
>>> https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01569.html
>>> => Unfortunately I forgot to change the Title to [PATCHv2] or so.
>>> Should I send a ping for this one?
>>>
>>> [PATCHv2] Handle overlength strings in the C FE
>>> https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01566.html
>>> => Should I send a ping for this one?
>> No need to ping. I've got it here. What's odd is that it's regressing
>> 87053 .
> Which is probably a sign that we've got an incorrect test for NUL
> termination somewhere.
I think I've found the issue. I've got more testing to do, but looks
like a thinko on my part.
jeff
next prev parent reply other threads:[~2018-09-06 22:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 13:13 Bernd Edlinger
2018-08-26 5:36 ` Jeff Law
2018-08-26 8:52 ` Bernd Edlinger
2018-08-29 21:11 ` Jason Merrill
2018-09-03 3:44 ` Jeff Law
2018-09-03 12:35 ` Bernd Edlinger
2018-09-04 14:31 ` Jeff Law
2018-09-06 11:05 ` Bernd Edlinger
2018-09-06 15:44 ` Jeff Law
2018-09-06 17:12 ` Bernd Edlinger
2018-09-06 22:01 ` Jeff Law
2018-09-06 22:16 ` Jeff Law
2018-09-06 22:26 ` Jeff Law [this message]
2018-09-07 6:51 ` Bernd Edlinger
2018-09-07 13:36 ` Bernd Edlinger
2018-09-07 17:44 ` Bernd Edlinger
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=a09d3de8-8e73-d86a-2194-c415988386b7@redhat.com \
--to=law@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=nathan@acm.org \
--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).