Pushed macOS:
b1a351290bffd190ff190638b6f4c013b5991d6a
final/clang+llvm-4.0.0-x86_64-apple-darwin.tar.xz
—
Mehdi
> On Mar 10, 2017, at 2:07 PM, Khem Raj via llvm-dev
> wrote:
>
> On 17-03-10 13:10:25, Hans Wennborg wrote:
>> Hi Khem,
>>
>> On Fri, Mar 10, 2017 at 1:03 PM, Khem Raj via llvm
Hi Khem,
On Fri, Mar 10, 2017 at 1:03 PM, Khem Raj via llvm-dev
wrote:
> On Fri, Mar 10, 2017 at 7:01 AM, Renato Golin via llvm-dev
> wrote:
>> ARM and AArch64 looking good, uploaded.
>>
>
> This is not particularly related to this RC but in general with 4.0.0
> I am seeing a failure quite commo
On Thu, Mar 9, 2017 at 2:28 PM, Hans Wennborg wrote:
> On Wed, Mar 8, 2017 at 4:52 PM, Hans Wennborg wrote:
>> Dear testers,
>>
>> The final version of 4.0.0 was just tagged (from the 4.0 branch at
>> r297335). There were no changes after rc4.
>>
>> Please build the final binaries and upload to t
ARM and AArch64 looking good, uploaded.
4e62f3d5dcc95189eaec2d950950876a423f8a8c
clang+llvm-4.0.0-aarch64-linux-gnu.tar.xz
1b031f16683e3bcd779f50e6d47d0d1f3f265e9f
clang+llvm-4.0.0-armv7a-linux-gnueabihf.tar.xz
On 10 March 2017 at 12:14, Ben Pope via cfe-dev wrote:
> On 09/03/17 00:52, Hans Wenn
Hi,
I'm working on a crash reporter tool that invokes and controls lldb through a
batchfile. As described
(http://stackoverflow.com/questions/26267289/how-can-i-exit-lldb-after-running-commands-with-o)
it is tricky to get older lldb versions to exit cleanly because they don't
react as they sho
Trying to evaluate:
((unsigned short* (*)(void *))10544800)((void*)44769264)
or
((unsigned short* (*)(void *))_ElementsGetTypeName)((void*)44769264)
in lldb/windows gives me
Unsupported instruction: %call = call i16* inttoptr (i32 16967328 to
i16* (i8*)*)(i8* inttoptr (i32 15867888 to i8*))
