I replied on the "has been tagged" thread; I couldn't find the binary
on the sftp. Maybe you uploaded the wrong version, or in some other
folder?
On Mon, Aug 22, 2016 at 4:01 PM, Renato Golin wrote:
> Hi Hans,
>
> I did upload the aarch64 binary, didn't you find it? Maybe I uploaded the
> wrong o
Hi Hans,
I did upload the aarch64 binary, didn't you find it? Maybe I uploaded the
wrong one?
Cheers,
Renato
On 22 Aug 2016 7:55 p.m., "Hans Wennborg via Release-testers" <
release-test...@lists.llvm.org> wrote:
> We're getting close to the final release. I know the schedule on the
> web page s
Hello everybody,
Just want to let you know that the first LLVM Social in Berlin will happen this
Thursday, 19:00 CET.
The place is a nice co-working space/cafe called Betahaus:
https://www.google.com/maps?f=q&hl=en&q=Prinzessinnenstrasse+19-20+10969,+,+Berlin,+de
Looking forward to meet you all
We don't want to make ELFOSABI_NONE mean Linux. ELFOSABI_NONE is historically
ELFOSABI_SYSV, and used by a lot of things. So not all core files identified as
ELFOSABI_NONE are Linux.
Whe lldb loads a core file with a target binary, it will merge the 2 triples.
If it can't identify the OS from
We're getting close to the final release. I know the schedule on the
web page says 'final' should be tagged today, but I still think it
should be possible to get there this week.
Source and binaries for LLVM-3.9.0-rc2 are now available at
http://llvm.org/pre-releases/3.9.0/#rc2
Please try it out
On Sat, Aug 20, 2016 at 2:45 PM, Sylvestre Ledru wrote:
> Le 19/08/2016 à 03:51, Hans Wennborg via Release-testers a écrit :
>>
>> Dear testers,
>>
>> 3.9.0-rc2 was just tagged from the 3.9 branch at r279183.
>>
>> This is a release candidate in the very real sense that if nothing new
>> comes up,
> On Aug 22, 2016, at 6:00 AM, Howard Hellyer via lldb-dev
> wrote:
>
> I've been trying to understand why some Linux core files fail to load in
> lldb.
>
> The problem seems to be that in the ELF header Linux uses the ELFOSABI_NONE
> (0x0) value rather than ELFOSABIT_LINUX (0x3).If I eithe
I've been trying to understand why some Linux core files fail to load in
lldb.
The problem seems to be that in the ELF header Linux uses the
ELFOSABI_NONE (0x0) value rather than ELFOSABIT_LINUX (0x3).If I either
change the e_ident[EI_OSABI] byte to 0x3 in the header or the code in
ArchSpec.cp
On 19 August 2016 at 22:10, Kate Stone via lldb-dev
wrote:
> Following up from yesterday, everything now builds and runs cleanly with the
> configuration described below on macOS. I did have to make one set of minor
> changes to preserve #include ordering, but that’s already committed to trunk
>
