search for: llvm28

Displaying 8 results from an estimated 8 matches for "llvm28".

Did you mean: llvm2
2011 Dec 16
3
[LLVMdev] llvm/clang test failures on powerpc-darwin8
...> Jack Hi Jack, I never managed to successfully build llvm29 on powerpc-darwin8, after running into some build issues, and having filed bug 9958, I got the impression of ppc-darwin being "not supported", so I didn't put much more effort into it back then. However llvm28 did build, and I still have it installed and hidden away. (It looks like *someone* runs ppc-darwin a buildbot, but not for darwin8.) Knowing what I've learned so far, the effort would be similar, perhaps even duplicate to just trying to fix things directly with g++-4.0.1. Time will tell,...
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
...bsite is not complete... Is there >> any way i can force the generation of these tables in current LLVM? >> >> Thanks in advance, >> Yiannis >> Hi Duncan, Sorry for my omission! I attach an example (test_0.ll). I do: llvm-as < test_0.ll | llc and i get output-llvm28.txt with the 2.8 versions of the tools and i repeat with the latest versions from the svn repo and i get output-llvm30.txt. As you can see there is a: .section .gcc_except_table,"a", at progbits .... in the 2.8 output just below the code segment while there is no such section...
2011 Dec 16
0
[LLVMdev] llvm/clang test failures on powerpc-darwin8
...t; Hi Jack, > I never managed to successfully build llvm29 on powerpc-darwin8, after > running into some build issues, and having filed bug 9958, I got the > impression of ppc-darwin being "not supported", so I didn't put much more > effort into it back then. However llvm28 did build, and I still have it > installed and hidden away. (It looks like *someone* runs ppc-darwin a > buildbot, but not for darwin8.) Knowing what I've learned so far, the > effort would be similar, perhaps even duplicate to just trying to fix > things directly with g++-4...
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
Hi Yiannis, > I have been using llvm 2.8 (i know ancient history!) for a backend that i was > implementing. I have been trying to port my patches to latest llvm (svn build) > lately but i have one problem as far as the Exception Handling mechanism is > concerned. It seems that there are no Exception Tables generated any more such > as the one below: got some example bitcode for
2011 Sep 02
2
[LLVMdev] Exception Tables in latest LLVM
Hey everybody! I have been using llvm 2.8 (i know ancient history!) for a backend that i was implementing. I have been trying to port my patches to latest llvm (svn build) lately but i have one problem as far as the Exception Handling mechanism is concerned. It seems that there are no Exception Tables generated any more such as the one below: .section .gcc_except_table,"a", at
2011 Sep 02
0
[LLVMdev] Exception Tables in latest LLVM
...>> any way i can force the generation of these tables in current LLVM? >>> >>> Thanks in advance, >>> Yiannis >>> > Hi Duncan, > > Sorry for my omission! I attach an example (test_0.ll). I do: > llvm-as < test_0.ll | llc > and i get output-llvm28.txt with the 2.8 versions of the tools and i repeat with > the latest versions from the svn repo and i get output-llvm30.txt. > > As you can see there is a: > .section .gcc_except_table,"a", at progbits > .... > in the 2.8 output just below the code segment while there i...
2011 Dec 16
0
[LLVMdev] llvm/clang test failures on powerpc-darwin8
On Fri, Dec 16, 2011 at 01:51:57AM -0500, David Fang wrote: > Hi, > Thanks for the quick reply again. > >> On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote: >>> Hi, >>> >>> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and >>> have the following test results to share. >>>
2011 Dec 16
3
[LLVMdev] llvm/clang test failures on powerpc-darwin8
Hi, Thanks for the quick reply again. > On Thu, Dec 15, 2011 at 1:17 PM, David Fang <fang at csl.cornell.edu> wrote: >> Hi, >> >> I've bootstrapped llvm/clang from svn-trunk on powerpc-darwin8 (g++-4.0.1), and >> have the following test results to share. >> Summary below, full log at: >>