Hi Chris,
On Thu, Nov 24, 2011 at 10:43 PM, Pekka Enberg <penberg@xxxxxxxxxx> 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?
On Fri, Nov 25, 2011 at 10:05 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote:
> 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?
Well, sure, that would be the perfect solution.
Unfortunately, I'm not at all familiar with the C++ API. I did look at
just adding the LLVM 3.0 LLVMStructCreateNamed() and
LLVMStructSetBody() wrappers on top of LLVM 2.8 but they don't compile
because StructType API changed. So it's not going to be as simple as
copy-pasting the missing functions to sparse.git.
On Thu, Nov 24, 2011 at 10:43 PM, Pekka Enberg <penberg@xxxxxxxxxx> wrote:
>> 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.
On Fri, Nov 25, 2011 at 10:05 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote:
> Still, it will take a while for the distribution to update to the new version.
Sure.
Do you consider this to be a merge blocker? I'd personally just go
forward with LLVM 3.0 and add the compat wrappers along the way if
there are people who actually care about it.
Pekka
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
