From: Pekka Enberg <penberg@kernel.org>
To: Derek M Jones <derek@knosof.co.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
Christopher Li <sparse@chrisli.org>,
linux-sparse@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Josh Triplett <josh@joshtriplett.org>
Subject: Re: [ANNOUNCE] LLVM backend for Sparse
Date: Mon, 29 Aug 2011 18:45:39 +0300 [thread overview]
Message-ID: <CAOJsxLHj1u9ccjvT3Z4yqHsou2mSUhLFpefvpN_WHDvimnTqyQ@mail.gmail.com> (raw)
In-Reply-To: <4E5BB37E.7090905@knosof.co.uk>
On Mon, Aug 29, 2011 at 6:42 PM, Derek M Jones <derek@knosof.co.uk> wrote:
>>> Can people allay my concern that this work is not on the slippery
>>> slope leading to sparse becoming the recommended compiler for
>>> building the kernel?
>>
>> I doubt sparse will ever have the testing, support and deployment
>> infrastructure of the gcc ecosystem.
On Mon, Aug 29, 2011 at 6:42 PM, Derek M Jones <derek@knosof.co.uk> wrote:
> Exactly. Unfortunately people's desire to control their world is often
> stronger.
I doubt sparse will ever become the 'recommended compiler' for Linux
but I fail to see why that would be a bad thing.
Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-08-29 15:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-28 6:08 [ANNOUNCE] LLVM backend for Sparse Pekka Enberg
2011-08-28 8:51 ` Christopher Li
2011-08-28 13:51 ` Pekka Enberg
2011-08-28 14:01 ` Pekka Enberg
2011-08-28 16:54 ` Linus Torvalds
2011-08-29 7:41 ` Pekka Enberg
2011-08-29 9:19 ` Christopher Li
2011-08-29 11:05 ` Pekka Enberg
2011-08-29 14:22 ` Pekka Enberg
2011-08-29 15:14 ` Derek M Jones
2011-08-29 15:33 ` Jeff Garzik
2011-08-29 15:42 ` Derek M Jones
2011-08-29 15:45 ` Pekka Enberg [this message]
2011-08-29 16:58 ` Linus Torvalds
2011-08-29 15:27 ` Jeff Garzik
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=CAOJsxLHj1u9ccjvT3Z4yqHsou2mSUhLFpefvpN_WHDvimnTqyQ@mail.gmail.com \
--to=penberg@kernel.org \
--cc=derek@knosof.co.uk \
--cc=jeff@garzik.org \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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.