search for: release_350

I’m sorry for the late announcement. The binaries for the 3.5 release candidate 2 are now available. Please pick them up here and test them out! http://llvm.org/pre-releases/3.5/ -bw -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140811/c65347b7/attachment.html>

...e candidate 2 are now available. Please >> pick them up here and test them out! >> >> http://llvm.org/pre-releases/3.5/ > > Can somebody entertain me and tag libcxxabi please? > > I'm expecting something here: > http://llvm.org/svn/llvm-project/libcxxabi/tags/RELEASE_350/rc2/ > > Much appreciated, > This looks like it hasn’t been released since 3.0. Is it still in development? -bw

...quot;no-nans-fp-math"="false" "stack-protector-buffer-size"="8" "unsafe-fp-math"="false" "use-soft-float"="false" } attributes #2 = { nounwind } !llvm.ident = !{!0} !0 = metadata !{metadata !"clang version 3.5.0 (tags/RELEASE_350/final) ()"} Here is the assembly generated by llc (I'm not sure that's what you meant by 'final assembly'): .text .file "foo_bar.ll" .globl main .align 16, 0x90 .type main, at function main:...

...:$ ./test-clang++ Illegal instruction Note that the following assignment still works: re.assign(static_cast<std::regex const&>(std::regex("foo"))); I'm working on Debian 8.0, my clang version is: ptomulik at barakus:$ clang++ --version Debian clang version 3.5.0-9 (tags/RELEASE_350/final) (based on LLVM 3.5.0) Target: x86_64-pc-linux-gnu Thread model: posix Where should I report the bug? Regards! -- Pawel Tomulik

..."no-nans-fp-math"="false" > "stack-protector-buffer-size"="8" "unsafe-fp-math"="false" > "use-soft-float"="false" } > > !llvm.ident = !{!0} > > !0 = metadata !{metadata !"clang version 3.5.0 (tags/RELEASE_350/final > 217949)"} > > (Note changed triple and compiler version. Also note i'm not using > "target-cpu" argument now as "cortex-a8" is not supported for this triple). > > Next i'm trying to interpret it (source code is copy-pasted from lli tool &gt...

Both Clang/LLVM 3.4 -> Clang/LLVM 3.5 And i will also try using MCJIT. 2014-09-17 18:56 GMT+06:00 Anton Smirnov <dev at antonsmirnov.name>: > Hi, Tim. > > I've used Clang 3.4 final release and now i'm going to test it with 3.5 > release (since i've read about arm64 improvements). > I will report my results. > > BTW, is it possible to get smth like

...t;>> "stack-protector-buffer-size"="8" "unsafe-fp-math"="false" >>> "use-soft-float"="false" } >>> >>> !llvm.ident = !{!0} >>> >>> !0 = metadata !{metadata !"clang version 3.5.0 (tags/RELEASE_350/final >>> 217949)"} >>> >>> (Note changed triple and compiler version. Also note i'm not using >>> "target-cpu" argument now as "cortex-a8" is not supported for this triple). >>> >>> Next i'm trying to interpret...

Hi, I'm having trouble using virtual register in the X86 backend. I implemented a new intrinsic and I use a custom inserter. The goal of the intrinsic is to set the content of the stack to zero at the end of each function. Here is my code: MachineBasicBlock * X86TargetLowering::EmitBURNSTACKWithCustomInserter( MachineInstr *MI, MachineBasicBlock

...size"="8" "unsafe-fp-math"="false" >>>>> "use-soft-float"="false" } >>>>> >>>>> !llvm.ident = !{!0} >>>>> >>>>> !0 = metadata !{metadata !"clang version 3.5.0 (tags/RELEASE_350/final >>>>> 217949)"} >>>>> >>>>> (Note changed triple and compiler version. Also note i'm not using >>>>> "target-cpu" argument now as "cortex-a8" is not supported for this triple). >>>>> >&g...

Hi Xin, Thank you for your reply! I have tried the 3 alias analyses you have mentioned on LLVM 3.5: 1) $ opt -globalsmodref-aa -aa-eval < xxx.bc > /dev/null (May-alias response 100%) 2) $ opt -tbaa -aa-eval < xxx.bc > /dev/null (May-alias response 100%) 3) $ opt -cfl-aa -aa-eval < xxx.bc> /dev/null (Unknown command line argument '-cfl-aa') It seems that they are not