Re: suggestion for Merging LLVM

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Nov 21, 2011 at 10:01 PM, Pekka Enberg <penberg@xxxxxxxxxx> wrote:
> Agreed.
>
> I'd actually prefer that we keep the full history for one simple reason:
> the commit changelogs. They provide valuable information on why we've
> implemented the things the way we have.

OK, I will just do the git merge then. Can you generate a pull request?

I just check out the sparse-llvm, the tip of the tree is broken for me:

     CC       sparse-llvm.o
sparse-llvm.c: In function ‘sym_struct_type’:
sparse-llvm.c:117:2: warning: implicit declaration of function
‘LLVMStructCreateNamed’ [-Wimplicit-function-declaration]
sparse-llvm.c:117:6: warning: assignment makes pointer from integer
without a cast [enabled by default]
sparse-llvm.c:129:2: warning: implicit declaration of function
‘LLVMStructSetBody’ [-Wimplicit-function-declaration]
     LINK     sparse-llvm
sparse-llvm.o: In function `sym_struct_type':
/export/git/sparse-llvm/sparse-llvm.c:117: undefined reference to
`LLVMStructCreateNamed'
/export/git/sparse-llvm/sparse-llvm.c:129: undefined reference to
`LLVMStructSetBody'
collect2: ld returned 1 exit status

I am using llvm 2.9, I guess my llvm is too new?

Chris
--
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


[Index of Archives]     [Newbies FAQ]     [LKML]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Trinity Fuzzer Tool]

  Powered by Linux