- User Since
- Nov 19 2014, 11:12 AM (280 w, 6 d)
Apr 20 2017
Sep 7 2016
Cool. Would it be a good idea to only use LLVM's demangler? We can get rid of all the messy ifdef business, and I assume the LLVM demangler would be better maintained and more up to date than any system demangler.
Jul 18 2016
May 23 2016
May 4 2016
We don't test host-only Windows. It's passing Windows to Android though.
What's the reason that it fails on Windows?
Apr 29 2016
Apr 28 2016
Apr 27 2016
Apr 25 2016
Apr 20 2016
Apr 18 2016
Mar 25 2016
Mar 17 2016
Remove usage of LLVM_PREFIX altogether.
Mar 14 2016
Mar 2 2016
Mar 1 2016
Feb 26 2016
Check return value of GetScalarValue directly.
Feb 25 2016
Feb 23 2016
Use target instead of sc.target_sp.get().
Jan 28 2016
Nov 6 2015
I'm still not quite sure how this works, but changing:
Hi, do you think this could have affected thread specific breakpoints? It seems a bit suspicious that TestThreadSpecificBreakpoints.py started timing out completely after this change and rL252356.
Nov 5 2015
I haven't seen anything else that uses LLVM_OPTIONAL_SOURCES, but it's conceivable that there might be items in the list already, and I would like to avoid doing anything to it besides just appending.
It's not actually CMake complaining but the LLVM cmake scripts.
LLVM_OPTIONAL_SOURCES should avoid that.
I've reverted this change to get the builders running again. Hope you don't mind.
The LLVM cmake project doesn't like having cpp files lying around that don't get used. So this actually breaks the build on all non-darwin systems.
Nov 4 2015
Yeah, it seems like it's been passing for gcc-4.9 for a while now. Thanks
Fixed with http://reviews.llvm.org/rL252124
Hi, this breaks all of our linux builders:
Oct 28 2015
Seems legit. But I've never built standalone, so I probably shouldn't be a reviewer for this.
Oct 27 2015
Oct 6 2015
Sep 22 2015
Sep 21 2015
Remove existing workaround.
Do we still need the original stepInstruction?
Sep 18 2015
I thought this was supposed to be fixed, but TestChangeProcessGroup, TestExpressionInSyscall, and TestRegisters just started failing for me recently because of this.
Remove old line.
Sep 17 2015
Could you please take a look at these issues?