From: Linus Torvalds <torvalds@linux-foundation.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Marco Elver <elver@google.com>, Borislav Petkov <bp@suse.de>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH] sparse: use the _Generic() version of __unqual_scalar_typeof()
Date: Wed, 8 Jul 2020 12:02:17 -0700 [thread overview]
Message-ID: <CAHk-=wgRDFAkN-KNpVWUbf=1RUGn3=nMx6aZ7z2X9OhH5db-Og@mail.gmail.com> (raw)
In-Reply-To: <20200618222620.5069-1-luc.vanoostenryck@gmail.com>
On Thu, Jun 18, 2020 at 3:26 PM Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
>
> If the file is being checked with sparse, use the version of
> __unqual_scalar_typeof() using _Generic(), leaving the unoptimized
> version only for the oldest versions of GCC.
Side note: for unrelated reasons I decided to try to just raise the
gcc minimum to 4.9, which then makes this patch redundant. The old
non-_Generic() case simply doesn't exist any more.
Of course, maybe somebody screams about having to use some gcc-4.8
version in their environment so much that I'll revert it, but I doubt
it. gcc-4.8 had lots of problems.
Linus
prev parent reply other threads:[~2020-07-08 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 22:26 [PATCH] sparse: use the _Generic() version of __unqual_scalar_typeof() Luc Van Oostenryck
2020-06-19 8:23 ` Will Deacon
2020-06-19 9:51 ` Marco Elver
2020-06-19 14:12 ` Luc Van Oostenryck
2020-06-19 18:26 ` Linus Torvalds
2020-06-19 19:08 ` Luc Van Oostenryck
2020-06-20 4:32 ` kernel test robot
2020-07-08 19:02 ` Linus Torvalds [this message]
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='CAHk-=wgRDFAkN-KNpVWUbf=1RUGn3=nMx6aZ7z2X9OhH5db-Og@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=bp@suse.de \
--cc=elver@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).