All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Christopher Li <sparse@chrisli.org>,
	Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] sparse/parse.c: ignore hotpatch attribute
Date: Thu, 30 Apr 2015 10:51:42 -0700	[thread overview]
Message-ID: <CA+55aFxCTx32CPkHCJM1NNv67vKHo-6yuTiLOg2Ya-=pn=O36g@mail.gmail.com> (raw)
In-Reply-To: <20150430173823.GA9379@cloud>

On Thu, Apr 30, 2015 at 10:38 AM,  <josh@joshtriplett.org> wrote:
>
> I think part of the problem arises because sparse claims (via the
> preprocessor symbols we provide) to be whatever version of GCC it was
> compiled with.  I think that's a mistake.  We should pick a version of
> GCC for which we support all the attributes we actually need to do
> something with, and advertise ourselves specifically as that version.

Fair enough. Although there may then be headers that are unhappy.

> I suspect that 3.2 is probably the version sparse should claim to be,
> for now.

That may be too old. You can't reliably compile the kernel with gcc
that old (some config options will complain).

At least CONFIG_GCOV_KERNEL wants 3.4 minimum.

                       Linus

  reply	other threads:[~2015-04-30 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 10:48 [PATCH] sparse/parse.c: ignore hotpatch attribute Heiko Carstens
2015-04-29 23:22 ` Christopher Li
2015-04-30 11:47   ` Heiko Carstens
2015-04-30 15:45 ` Linus Torvalds
2015-04-30 15:50   ` Nicholas Mc Guire
2015-04-30 17:38   ` josh
2015-04-30 17:51     ` Linus Torvalds [this message]
2015-04-30 19:41       ` josh

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='CA+55aFxCTx32CPkHCJM1NNv67vKHo-6yuTiLOg2Ya-=pn=O36g@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-sparse@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.