From: Jeff Garzik <jeff@garzik.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Pekka Enberg <penberg@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: suggestion for Merging LLVM
Date: Fri, 25 Nov 2011 12:52:09 -0500 [thread overview]
Message-ID: <4ECFD5C9.20702@garzik.org> (raw)
In-Reply-To: <CANeU7QkiPcdzQYf9QBdSZ0UmOJGNE2ijk1Ys0dAVeS6tGaS+Zw@mail.gmail.com>
On 11/25/2011 03:05 AM, Christopher Li wrote:
> On Thu, Nov 24, 2011 at 10:43 PM, Pekka Enberg<penberg@kernel.org> wrote:
>> I wasn't able to find out any C API for that and assume it was only
>> possible with the C++ API. That said, I'd also be happy to use
>> something else to be compatible with older versions if there is one.
>> Any LLVM experts on the list?
>
> If it just need to use the C++ API, we can compile a bridge c++ file
> to export the missing C++ API to C file. It is actually pretty common praticse
> if you play with LLVM internal a lot, some API just don't exist in C yet.
> We are already using g++ to link llvm, one more c++ file could not hurt.
> If we need some C++ only API later, we can add it there as well.
>
> What do you say?
>
>> LLVM 3.0 is going to be released "real soon now" so I don't think it's
>> a problem in practice. We'd need to add a version check, though so we
>> don't break build on machines that have older LLVM installed.
>
> Still, it will take a while for the distribution to update to the new version.
Pulling in bits of LLVM itself into sparse, to make older versions work,
seems like a mess of work and maintenance without a driving need. Just
note that 3.0 is required, and things will sort themselves out in time.
Jeff
next prev parent reply other threads:[~2011-11-25 17:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 2:43 suggestion for Merging LLVM Christopher Li
2011-11-22 5:52 ` Jeff Garzik
2011-11-22 6:01 ` Pekka Enberg
2011-11-22 20:32 ` Jeff Garzik
2011-11-22 20:38 ` Pekka Enberg
2011-11-23 4:11 ` Jeff Garzik
2011-11-23 6:01 ` Jeff Garzik
2011-11-23 6:58 ` Pekka Enberg
2011-11-25 1:45 ` Christopher Li
2011-11-25 2:25 ` Jeff Garzik
2011-11-25 5:52 ` Pekka Enberg
2011-11-25 6:28 ` Christopher Li
2011-11-25 6:43 ` Pekka Enberg
2011-11-25 8:05 ` Christopher Li
2011-11-25 8:29 ` Pekka Enberg
2011-11-25 17:52 ` Jeff Garzik [this message]
2011-11-25 19:13 ` Christopher Li
2011-11-25 20:18 ` Jeff Garzik
2011-11-25 20:30 ` Christopher Li
2011-12-13 20:29 ` Pekka Enberg
2011-12-15 21:34 ` Christopher Li
2011-12-20 8:53 ` Pekka Enberg
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=4ECFD5C9.20702@garzik.org \
--to=jeff@garzik.org \
--cc=linux-sparse@vger.kernel.org \
--cc=penberg@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.