Hello, Bill> It may be my lack of understanding, but it appears that having -- > enable-eh set during compilation of llvm-gcc is causing extra files > to be compiled.Oh, no. They are always compiled.> They do. However, it doesn't seem to stop it from failing during > compilation of unwind-dw2.c for libgcc -- it has > "__builtin_eh_return" in it. During 4-way FAT PPC compilation, it > tries to compile this file and fails during the LowerOperation > function. Turning --enable-eh off makes the error go away.Could you please send me .bc, which fails? I'll try to figure out, what is going wrong. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.
On 8/29/07, Bill Wendling <isanbard at gmail.com> wrote:> On 8/29/07, Anton Korobeynikov <asl at math.spbu.ru> wrote: > > Hello, Bill > > > > > It may be my lack of understanding, but it appears that having -- > > > enable-eh set during compilation of llvm-gcc is causing extra files > > > to be compiled. > > Oh, no. They are always compiled. > > > > > They do. However, it doesn't seem to stop it from failing during > > > compilation of unwind-dw2.c for libgcc -- it has > > > "__builtin_eh_return" in it. During 4-way FAT PPC compilation, it > > > tries to compile this file and fails during the LowerOperation > > > function. Turning --enable-eh off makes the error go away. > > Could you please send me .bc, which fails? I'll try to figure out, what > > is going wrong. > > > Here's the attached .ll file. Please use -march=ppc and/or ppc64. >And now the bugpoint reduced bc file. -bw -------------- next part -------------- A non-text attachment was scrubbed... Name: bugpoint-reduced-simplified.bc Type: application/octet-stream Size: 640 bytes Desc: not available URL: <lists.llvm.org/pipermail/llvm-dev/attachments/20070829/66263c27/attachment.obj>
Reasonably Related Threads
- [LLVMdev] RFC: Patch for Exceptions
- [LLVMdev] RFC: Patch for Exceptions
- Possible stack corruption during call to JITSymbol::getAddress()
- Possible stack corruption during call to JITSymbol::getAddress()
- Possible stack corruption during call to JITSymbol::getAddress()