http://llvm.org/bugs/show_bug.cgi?id=2751
Bruno Cardoso Lopes <[EMAIL PROTECTED]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #7 from Bruno Cardoso Lopes <[EMAIL PROTECTED]> 2008-09-15
16:13:33 ---
Hi Patrice,
Fixed :
http://llvm.org/viewvc/llvm-project?view=rev&revision=56228
I suggest that you generate Mips bytecode instead of x86, this can be
accomplished using cc1 generated by the llvm-gcc mips cross-compilation, even
when the compilation breaks.
If you configured llvm-gcc obj dir as /p/llvm-gcc/mips/obj/, you'll find cc1 in
/p/llvm-gcc/mips/obj/gcc/cc1 after the compilation breaks. So you must use it
to
generate the mips bytecode.
Using the x86 bytecode as input for the mips back-end (see the target-triple of
the bytecode you attached) can lead to strange behaviors.
Thanks. :)
--
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
LLVMbugs mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/llvmbugs
