[lldb-dev] Moderators for the 2017 LLVM Developers' Mtg Needed!

2017-09-26 Thread Tanya Lattner via lldb-dev 
The 2017 LLVM Developers’ Meeting relies on volunteers to keep things running 
smoothly. Moderators are critical to this as they keep speakers on track and 
facilitate Q&A after the talk. I’m looking for community members who would be 
attending specific talks anyway, to volunteer to moderate the session.

If you are interested in volunteering, please respond to this email with your 
first and second choice session times. You will moderate all talks during that 
time slot and they will occur back to back in the same room. Moderators 
introduce the speaker, give the speaker warnings about time, and facilitate Q&A 
by running microphones.

Full schedule here: https://2017llvmdevmtg.sched.com

Session 1 (10:30-12:45, Technical Track)
Dominator Trees and incremental updates that transcend time
GlobalISel: Past, Present, and Future
XRay in LLVM: Function Call Tracing and Analysis

Session 2 (2:15-4:00PM, General Session)
LIGHTNING TALKS
LLVM Compile-Time: Challenges. Improvements. Outlook.

Session 3 (2:15-4:00PM, Technical Track)
Tutorial: Welcome to the back-end: The LLVM machine representation.
Scale, Robust and Regression-Free Loop Optimizations for Scientific Fortran and 
Modern C++

Session 4 (4:20-5:50PM, General Session)
The Type Sanitizer: Free Yourself from -fno-strict-aliasing
Structure-aware fuzzing for Clang and LLVM with libprotobuf-mutator

Session 5 (4:20-6:05PM, General Session)
Vectorizing Loops with VPlan – Current State and Next Steps
Tutorial: Writing Great Machine Schedulers

Session 6 (9:00-10:45AM, General Session)
Falcon: An optimizing Java JIT
Apple LLVM GPU Compiler: Embedded Dragons

Session 7 (10:00-10:45AM, Technical Track)
eval() in C++

Session 8 (11:10AM-12:40PM, General Session)
Implementing Swift Generics
The Further Benefits of Explicit Modularization: Modular Codegen

Session 9 (11:10AM-12:40PM, Technical Track)
Bringing link-time optimization to the embedded world: (Thin)LTO with Linker 
Scripts
lld: A Fast, Simple, and Portable Linker

Session 10 (2:10-3:40PM, General Session)
Adding Index‐While‐Building and Refactoring to Clang
Advancing Clangd: Bringing persisted indexing to Clang tooling

Session 11 (2:10-3:40PM, Technical Track)
Enabling Parallel Computing in Chapel with Clang and LLVM
 Challenges when building an LLVM bitcode Obfuscator

Session 12 (4:40-6:25PM, General Session)
Building Your Product Around LLVM Releases
Tutorial: Head First into GlobalISel


Thanks,
Tanya

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

Re: [lldb-dev] [Bug 34676] check-lldb target fails on Windows due to incomplete compiler path

2017-09-26 Thread Carlos Alberto Enciso via lldb-dev 
Hi Adrian,

As you are working on the above Windows issue, I am assuming you are
running LLDB on Windows.
I have managed to build LLDB on Windows 10, after getting the correct
dependencies.

But from the LLDB home page, it seems that LLDB is only built and no tests
are run:

   - LLDB Windows Server 2008 x86 (CMake, MSVS 2013, Windows SDK 8.1, no
   tests) 
   - LLDB Windows 7 x86 (CMake, MSVS 2013, Windows SDK 8.1, no tests)
   

I run the tests via 'check-lldb' and these are the results:

63>  ===

63>  Test Result Summary

63>  ===

63>  Test Methods:   1299

63>  Reruns:   68

63>  Success: 365

63>  Expected Failure:233

*63>  Failure:  34*

63>CUSTOMBUILD : error : 14

63>  Exceptional Exit:  0

*63>  Unexpected Success:5*

63>  Skip:648

63>  Timeout:   0

63>  Expected Timeout:  0

I am wondering if these results match yours.

Thanks very much,

Carlos Enciso

On Tue, Sep 19, 2017 at 11:08 PM, via lldb-dev 
wrote:

> Adrian McCarthy  changed bug 34676
> 
> What Removed Added
> Assignee lldb-dev@lists.llvm.org amcca...@google.com
>
> *Comment # 1  on bug 34676
>  from Adrian McCarthy
>  *
>
> I'm starting with git bisect to see if I can pinpoint when this got broken.  
> It
> looks like it may have been a while back already.
>
> --
> You are receiving this mail because:
>
>- You are the assignee for the bug.
>
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Bug 34676] check-lldb target fails on Windows due to incomplete compiler path

2017-09-26 Thread Adrian McCarthy via lldb-dev 
I haven't spent too much time in LLDB lately.  The number of failures you
see seems a little high.  On Windows 7, I get:

===
Test Result Summary
===
Test Methods:   1301
Reruns:   28
Success: 387
Expected Failure:237
Failure:   4
Error:11
Exceptional Exit:  0
Unexpected Success:3
Skip:659
Timeout:   0
Expected Timeout:  0


On Tue, Sep 26, 2017 at 5:31 AM, Carlos Alberto Enciso <
international.phan...@gmail.com> wrote:

> Hi Adrian,
>
> As you are working on the above Windows issue, I am assuming you are
> running LLDB on Windows.
> I have managed to build LLDB on Windows 10, after getting the correct
> dependencies.
>
> But from the LLDB home page, it seems that LLDB is only built and no tests
> are run:
>
>- LLDB Windows Server 2008 x86 (CMake, MSVS 2013, Windows SDK 8.1, no
>tests) 
>- LLDB Windows 7 x86 (CMake, MSVS 2013, Windows SDK 8.1, no tests)
>
>
> I run the tests via 'check-lldb' and these are the results:
>
> 63>  ===
>
> 63>  Test Result Summary
>
> 63>  ===
>
> 63>  Test Methods:   1299
>
> 63>  Reruns:   68
>
> 63>  Success: 365
>
> 63>  Expected Failure:233
>
> *63>  Failure:  34*
>
> 63>CUSTOMBUILD : error : 14
>
> 63>  Exceptional Exit:  0
>
> *63>  Unexpected Success:5*
>
> 63>  Skip:648
>
> 63>  Timeout:   0
>
> 63>  Expected Timeout:  0
>
> I am wondering if these results match yours.
>
> Thanks very much,
>
> Carlos Enciso
>
> On Tue, Sep 19, 2017 at 11:08 PM, via lldb-dev 
> wrote:
>
>> Adrian McCarthy  changed bug 34676
>> 
>> What Removed Added
>> Assignee lldb-dev@lists.llvm.org amcca...@google.com
>>
>> *Comment # 1  on bug
>> 34676  from Adrian McCarthy
>>  *
>>
>> I'm starting with git bisect to see if I can pinpoint when this got broken.  
>> It
>> looks like it may have been a while back already.
>>
>> --
>> You are receiving this mail because:
>>
>>- You are the assignee for the bug.
>>
>>
>> ___
>> lldb-dev mailing list
>> lldb-dev@lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] EuroBSDcon2017 - The LLDB Debugger on NetBSD

2017-09-26 Thread Kamil Rytarowski via lldb-dev 
Hello,

I've uploaded my slides from the EuroBSDcon 2017 event about:

   "The LLDB Debugger on NetBSD"

to:

   http://netbsd.org/~kamil/eurobsdcon2017.html

There is a recording available on YouTube:

   https://youtu.be/qX0BS4P65cQ?t=16835



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

[lldb-dev] Docker Containers on Dockerhub for Releases

2017-09-26 Thread Gerald Wiltse via lldb-dev 
I just followed this effort which seems very useful for developers building
LLVM.

https://reviews.llvm.org/D34197

This email is to recommend that the LLVM team publish "official images" of
compiled LLVM and Clang similar to what the GCC team has done for users of
LLVM:

https://hub.docker.com/_/gcc/

This docker image has over 1 million pulls and hundreds of stars, a good
indicator that if you build it, it will have tremendous value to users who
need to just compile with it.   Information about how to enroll and publish
"official images" can be found here:

https://github.com/docker-library/official-images

The most significant use case for such official images is CI.  Travis CI
only has very old releases of most compilers, and so users often have to
spend 15 lines of Travis recipe to get the latest versions installed, while
the actual task of compiling can typically done in 1 line.


Gerald R. Wiltse
jerrywil...@gmail.com
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev