Re: [lldb-dev] PDB symbol reader supports C++ only?

2018-08-27 Thread Vadim Chugunov via lldb-dev
These two changes ([1]

[2]
)
appear to be sufficient to enable debugging of Rust binaries with pdb debug
info (make sure that msdia140.dll is somewhere lldb can find it).
At a cursory glance, I did not observe any ill effects of disabling that
language check, so I'm still not sure whether it was truly necessary, or
more of "Let's disable code paths we did not test".

As for allocating a language code for Rust, does Microsoft even have a
procedure for this?   In any case, looks like D folks had already staked out

0x44 for themselves.   I suggest we claim 0x27  :-)

On Mon, Aug 27, 2018 at 6:32 AM Tom Tromey  wrote:

> > "Vadim" == Vadim Chugunov via lldb-dev 
> writes:
>
> Vadim> Would you mind going into a bit more detail on what sort of
> Vadim> problems an unknown language could cause?  I'd like to understand
> Vadim> the issue before jumping in to fix anything.  AFAIK, in the case
> Vadim> of DWARF symbols, debug info for unknown languages is still used,
> Vadim> so it wouldn't be the first for LLDB...
>
> LLDB checks for DW_LANG_Rust and uses the C++ plugin in this case.
>
> The Rust lldb (
> https://github.com/rust-lang-nursery/lldb/commits/rust-release-70)
> removes this.
>
> If you get something working, let me know.  I'd like to incorporate it
> into the Rust lldb.
>
> Tom
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] PDB symbol reader supports C++ only?

2018-08-27 Thread Tom Tromey via lldb-dev
> "Vadim" == Vadim Chugunov via lldb-dev  writes:

Vadim> Would you mind going into a bit more detail on what sort of
Vadim> problems an unknown language could cause?  I'd like to understand
Vadim> the issue before jumping in to fix anything.  AFAIK, in the case
Vadim> of DWARF symbols, debug info for unknown languages is still used,
Vadim> so it wouldn't be the first for LLDB...

LLDB checks for DW_LANG_Rust and uses the C++ plugin in this case.

The Rust lldb 
(https://github.com/rust-lang-nursery/lldb/commits/rust-release-70)
removes this.

If you get something working, let me know.  I'd like to incorporate it
into the Rust lldb.

Tom
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [cfe-dev] [7.0.0 Release] rc2 has been tagged

2018-08-27 Thread Hans Wennborg via lldb-dev
That libclang dylib just implements an interface used for source code
indexing and such (https://clang.llvm.org/doxygen/group__CINDEX.html).
It's not used by the clang binary.

On Mon, Aug 27, 2018 at 1:26 PM, Marcus Johnson
 wrote:
> I'm just curious why you don't plan on using dlls? Xcode ships with libclang
> as a dylib, i wouldnt think windows would be a big leap?
>
>
> On Monday, August 27, 2018, Hans Wennborg  wrote:
>>
>> On Sat, Aug 25, 2018 at 12:03 AM, Marcus Johnson
>>  wrote:
>> >> Don't forget to compile (everything if possible, but especially LLVM)
>> >> as a
>> >> shared library on Windows.
>> >
>> > the installed toolchain is about 10 times bigger than the executable,
>> > because the static library is being compressed, which means on disk it's
>> > taking up far more space than it needs.
>>
>> If we had a way of building e.g. at least LLVM as a dll, maybe we
>> could do this, but currently the binaries are all statically linked
>> and there is no plan to change this.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc2 has been tagged

2018-08-27 Thread Dimitry Andric via lldb-dev
On 27 Aug 2018, at 10:29, Hans Wennborg  wrote:
> 
> On Sat, Aug 25, 2018 at 12:46 PM, Dimitry Andric  wrote:
...
>> Unfortunately the test-suite doesn't build on i386, since quite a few of its 
>> components requires SSE2, and the build shows many errors like:
>> 
>> /home/dim/llvm/7.0.0/rc2/test-suite.src/Bitcode/Benchmarks/Halide/blur/driver.cpp:37:29:
>>  error: always_inline function '_mm_set1_epi16' requires target feature 
>> 'sse2', but would be inlined into function 'blur_fast' that is compiled 
>> without support for 'sse2'
>>__m128i one_third = _mm_set1_epi16(21846);
>>^
> 
> The same problem must have been present also with 6.0.0 right?

Yes, this has apparently always been the case.  I'll make a note to either fix 
it post release, or to selectively skip building those tests for i386.

-Dimitry



signature.asc
Description: Message signed with OpenPGP
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


[lldb-dev] [7.0.0 Release] Release Candidate 2 source, docs, and binaries available

2018-08-27 Thread Hans Wennborg via lldb-dev
Hello everyone,

Source, docs, and binaries for LLVM 7.0.0-rc2 are now available at
https://prereleases.llvm.org/7.0.0/#rc2 (now with HTTPS, thanks
Anton!)

I'll add more binaries as they become available.

Please try it out and report any problems as bugs marked as blockers
of https://llvm.org/PR38406

Thanks,
Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [Release-testers] [7.0.0 Release] rc2 has been tagged

2018-08-27 Thread Hans Wennborg via lldb-dev
On Sat, Aug 25, 2018 at 12:46 PM, Dimitry Andric  wrote:
> On 23 Aug 2018, at 01:59, Hans Wennborg via Release-testers 
>  wrote:
>>
>> 7.0.0-rc2 was just tagged (from branch revision r340437).
>>
>> There have been a bunch of merges since rc1, and hopefully many of the
>> issues with the previous candidate are fixed in this one.
>
> By reverting r323281 locally, on top of rc2, I was now able to build and test 
> for i386-freebsd11 too.

Thanks! The revert will be part of rc3.

>
> Main test results on amd64-freebsd11 look better, roughly 2000 less failures, 
> mostly due to the libc++ get_timespec fix:
>
>   Expected Passes: 52409 (rc1: 50388)
>   Expected Failures  :   232 (rc1:   233)
>   Unsupported Tests  :  3687 (rc1:  3687)
>   Unexpected Passes  : 1 (rc1: 1)
>   Unexpected Failures:   491 (rc1:  2490)
>
> Test-suite test results on amd64-freebsd11:
>
>   Expected Passes: 845
>   Unexpected Failures: 61
>
> Test results on i386-freebsd11:
>
>   Expected Passes: 50186
>   Expected Failures  : 226
>   Unsupported Tests  : 2502
>   Unexpected Failures: 306
>
> Unfortunately the test-suite doesn't build on i386, since quite a few of its 
> components requires SSE2, and the build shows many errors like:
>
> /home/dim/llvm/7.0.0/rc2/test-suite.src/Bitcode/Benchmarks/Halide/blur/driver.cpp:37:29:
>  error: always_inline function '_mm_set1_epi16' requires target feature 
> 'sse2', but would be inlined into function 'blur_fast' that is compiled 
> without support for 'sse2'
> __m128i one_third = _mm_set1_epi16(21846);
> ^

The same problem must have been present also with 6.0.0 right?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [cfe-dev] [7.0.0 Release] rc2 has been tagged

2018-08-27 Thread Hans Wennborg via lldb-dev
On Sat, Aug 25, 2018 at 12:05 AM, Marcus Johnson
 wrote:
>>> Also, can you include Polly in the build as well?

I don't know how well Polly works on Windows. We've never had it in
the monthly snapshots (https://www.llvm.org/builds/), and that would
be a pre-requisite before bringing it into releases.

Tobias: does Polly work on Windows, and should we try to include it in
the snapshots?
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev


Re: [lldb-dev] [cfe-dev] [7.0.0 Release] rc2 has been tagged

2018-08-27 Thread Hans Wennborg via lldb-dev
On Sat, Aug 25, 2018 at 12:03 AM, Marcus Johnson
 wrote:
>> Don't forget to compile (everything if possible, but especially LLVM) as a
>> shared library on Windows.
>
> the installed toolchain is about 10 times bigger than the executable,
> because the static library is being compressed, which means on disk it's
> taking up far more space than it needs.

If we had a way of building e.g. at least LLVM as a dll, maybe we
could do this, but currently the binaries are all statically linked
and there is no plan to change this.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev