From: Martin Sebor <msebor@gmail.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
David Rientjes <rientjes@google.com>,
Ingo Molnar <mingo@kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Greg KH <gregkh@linuxfoundation.org>,
"Lendacky, Thomas" <thomas.lendacky@amd.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Willy Tarreau <w@1wt.eu>,
Xiongfeng Wang <wangxiongfeng2@huawei.com>
Subject: Re: [PATCH] Support the nonstring variable attribute (gcc >= 8)
Date: Tue, 13 Mar 2018 09:41:11 -0600 [thread overview]
Message-ID: <cc031f0f-7fc7-4bf1-c99e-020dbf41d836@gmail.com> (raw)
In-Reply-To: <CANiq72nZRzMDF2ZpT1rOnyMvx75XijRpuWbymThV9Uy06WOBrw@mail.gmail.com>
>>>> Martin Sebor also asked me about this, he's the one that worked on
>>>> the gcc code that introduced the warning. Sorry for not replying earlier.
>>>>
>>>
>>> Maybe you can pass this to him? (maybe open a bug in gcc's bugzilla?)
>>
>>
>> I've opened bug 84725 to extend attribute nonstring to the other
>> two character types:
>>
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84725
>>
>
> Thanks Martin! Please let us know whenever it is in the gcc trunk.
No problem. The patch has been committed into the trunk of GCC 8.
Let me know if there's something else. It may be too late to make
any more changes like this before GCC 8.1 is released but further
refinements to suppress false positives can be made in GCC 8.2.
Martin
next prev parent reply other threads:[~2018-03-13 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-17 19:10 [PATCH] Support the nonstring variable attribute (gcc >= 8) Miguel Ojeda
2018-02-18 23:20 ` David Rientjes
2018-02-19 0:01 ` Miguel Ojeda
2018-03-01 9:57 ` Arnd Bergmann
2018-03-02 17:36 ` Miguel Ojeda
2018-03-05 19:05 ` Martin Sebor
2018-03-07 12:20 ` Miguel Ojeda
2018-03-13 15:41 ` Martin Sebor [this message]
2018-03-13 15:57 ` Miguel Ojeda
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=cc031f0f-7fc7-4bf1-c99e-020dbf41d836@gmail.com \
--to=msebor@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=w@1wt.eu \
--cc=wangxiongfeng2@huawei.com \
--cc=will.deacon@arm.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