From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: christophe.leroy@c-s.fr, joe@perches.com,
Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-sparse@vger.kernel.org, sparse@chrisli.org
Subject: Re: Conflict between sparse and commit cafa0010cd51f ("Raise the minimum required gcc version to 4.6")
Date: Fri, 7 Sep 2018 20:37:53 +0200 [thread overview]
Message-ID: <20180907183751.zozqbmpq3dm4j3tw@ltop.local> (raw)
In-Reply-To: <CAKwvOdmXs+pWJGXu-zr-XSu7p-7hw=2m1vVQmVLwJcmGEFz0gg@mail.gmail.com>
On Fri, Sep 07, 2018 at 11:19:43AM -0700, Nick Desaulniers wrote:
> On Fri, Sep 7, 2018 at 11:13 AM Luc Van Oostenryck wrote:
> >
> > Sparse expand these macros to the same version than the compiler used
> > to compile GCC. I find a bit strange though to have sparse v0.5.2 but
> > using an old compiler.
>
> So Christophe must have a version of gcc < 4.6 installed somewhere?
It looks so.
> Does sparse use `cc`?
By default sparse use gcc (this can be overriden by using CC=...).
-- Luc
next prev parent reply other threads:[~2018-09-07 18:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81a5fd11-366c-0897-4143-d8d041420a41@c-s.fr>
2018-09-07 14:33 ` Conflict between sparse and commit cafa0010cd51f ("Raise the minimum required gcc version to 4.6") Christophe LEROY
2018-09-07 17:22 ` Nick Desaulniers
2018-09-07 18:13 ` Luc Van Oostenryck
2018-09-07 18:19 ` Nick Desaulniers
2018-09-07 18:37 ` Luc Van Oostenryck [this message]
2018-09-10 6:49 ` Christophe LEROY
2018-09-10 9:28 ` Luc Van Oostenryck
2018-09-10 9:56 ` Christophe Leroy
2018-09-10 11:34 ` Luc Van Oostenryck
2018-09-10 13:19 ` Christophe Leroy
2018-09-10 13:56 ` Luc Van Oostenryck
2018-09-10 14:05 ` Christophe LEROY
2018-09-10 15:15 ` Luc Van Oostenryck
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=20180907183751.zozqbmpq3dm4j3tw@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=sparse@chrisli.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