From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kamil Dudka <kdudka@redhat.com>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>,
Pekka J Enberg <penberg@cs.helsinki.fi>
Subject: Re: linearize bug?
Date: Sat, 27 Aug 2011 16:03:54 -0400 [thread overview]
Message-ID: <4E594DAA.8060401@garzik.org> (raw)
In-Reply-To: <CA+55aFxGwAXRWVcv_Qx6C4B_PKqzVVbc8O_znwUt_D6g1iDJvQ@mail.gmail.com>
On 08/27/2011 11:53 AM, Linus Torvalds wrote:
> On Sat, Aug 27, 2011 at 8:37 AM, Jeff Garzik<jeff@garzik.org> wrote:
>>
>> On our point of view, we probably prefer to simply turn off as many
>> transformations as possible. They just waste time, when an optimizing LLVM
>> backend is going to perform the same transformations anyway.
>
> I disagree - mainly because I don't think we're interested in the back
> end, are we?
>
> If we were doing LLVM hacking, then I'd agree. But as it is, we're
> supposed to improve sparse, not LLVM, so we should make sure that the
> _sparse_ output makes sense, and LLVM is just a code generator, no?
No idea Pekka's interest...
In general, my own decade-long goal has been to be able to play with a
kernel compiler other than gcc. That's why I wrote compile-i386 so long
ago, that's why the kernel got a bunch of LLVM-related bug fixes and C
cleanups, that's why I wrote the original sparse LLVM backend[1], and
why I'm working on Pekka's now.
So I'm definitely more interested in the backend side of things, and
tend to see simplifications and optimizations performed on the
linearized form as wasted work. sparse makes a great C front-end to a
compiler.
Obviously that's not the only PoV or use case of sparse, and is arguably
a crazy, unattainable goal in general... :)
Jeff
[1] https://patchwork.kernel.org/patch/19923/
next prev parent reply other threads:[~2011-08-27 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-27 6:29 linearize bug? Jeff Garzik
2011-08-27 11:34 ` Kamil Dudka
2011-08-27 15:29 ` Linus Torvalds
2011-08-27 15:37 ` Jeff Garzik
2011-08-27 15:53 ` Linus Torvalds
2011-08-27 16:54 ` Kamil Dudka
2011-08-27 17:13 ` Linus Torvalds
2011-08-27 17:27 ` Linus Torvalds
2011-08-27 19:26 ` Linus Torvalds
2011-08-27 20:03 ` Jeff Garzik [this message]
2011-08-28 6:26 ` Pekka Enberg
2011-08-27 23:39 ` [PATCH] cse: update PHI users when throwing away an instruction Kamil Dudka
2011-08-28 0:34 ` Linus Torvalds
2011-08-28 6:32 ` Christopher Li
2011-08-28 6:33 ` Pekka Enberg
2011-08-28 8:53 ` Jeff Garzik
2011-08-27 22:07 ` linearize bug? Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-11-12 4:09 Jeff Garzik
2006-11-13 4:43 ` Linus Torvalds
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=4E594DAA.8060401@garzik.org \
--to=jeff@garzik.org \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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 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).