From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kees Cook <keescook@chromium.org>,
linux-hardening@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH] gcc-plugins: fix gcc 11 indigestion with plugins...
Date: Mon, 11 Jan 2021 05:56:59 -0500 [thread overview]
Message-ID: <122278.1610362619@turing-police> (raw)
In-Reply-To: <CAMuHMdU1YSODgh_T5RxqUqorveAQiy_-gQbF_SwMEj7gvG25qw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Mon, 11 Jan 2021 10:47:23 +0100, Geert Uytterhoeven said:
> I guess this is the cause of the new "warning: invalid suffix on
> literal; C++11 requires a space between literal and string macro
> [-Wliteral-suffix]" with gcc 4.9 or 5.4?
Well, we fixed a #error, and picked up a warning. That's progress. ;)
It's probably related. I'm just having a hard time understanding why 4.9 and 5.4
whine about the lack of a space, while 8.3 and 11 didn't complain...
I'll see if I can cook up a patch that newer gcc are still happy with. You able
to easily test with 4.9 or 5.4?
[-- Attachment #2: Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2021-01-11 10:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-26 18:21 [PATCH] gcc-plugins: fix gcc 11 indigestion with plugins Valdis Klētnieks
2021-01-05 15:26 ` Josh Poimboeuf
2021-01-06 23:09 ` Kees Cook
2021-01-11 9:47 ` Geert Uytterhoeven
2021-01-11 10:56 ` Valdis Klētnieks [this message]
2021-01-11 11:02 ` Geert Uytterhoeven
2021-01-11 12:31 ` Valdis Klētnieks
2021-01-11 13:37 ` Josh Poimboeuf
2021-01-11 19:48 ` Kees Cook
2021-01-11 19:55 ` Valdis Klētnieks
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=122278.1610362619@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=geert@linux-m68k.org \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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