[lldb-dev] [SERVER UPDATE] Moving openmp, clang, clang-analyzer, libcxxabi, libcxx ... websites to new server

[Tanya Lattner via lldb-dev]

All,

The following websites will be moving to a new web server in the next few days:
clang.llvm.org 
clang-analyzer.llvm.org 
compiler-rt.llvm.org 
dragonegg.llvm.org 
klee.llvm.org 
libclc.llvm.org 
libcxx.llvm.org 
libcxxabi.llvm.org 
lldb.llvm.org 
lld.llvm.org 
openmp.llvm.org 
polly.llvm.org 
vmkit.llvm.org 

Please note that llvm.org  proper is NOT moving at this time. 
Therefore SVN, Bugzilla, ViewVC, and all the llvm.org/*  
webpages will remain on that server. I will be updating on this in a separate 
email.

How does this impact you?
You may see a very short downtime (< 1 hour) when the switch is made. This is 
most likely due to the DNS switch. I will notify the list when all websites 
listed have been moved. Since this does not involve SVN, the downtime is 
hopefully tolerable.

Are you fixing the SSL problem?
Yes. The new server will have SSL support for all websites and have an updated 
certificate. 

What about the website auto-update?
Currently, the web sites all automatically update via post-commit hook for SVN. 
We have temporarily set up an alternative method and websites will update every 
30 minutes.

What about website documentation generation?
There are 3 scripts that generate documentation on the web server. For doxygen, 
it will continue to update daily. For sphinx documentation, it will update 
every hour instead of immediately after a commit. 

In order to increase visibility into the server, these scripts have been 
enhanced to now email a list to indicate success or failure. You can either 
subscribe to the list or check the archives if you have concerns about 
documentation not being updated:
http://lists.llvm.org/cgi-bin/mailman/listinfo/www-scripts 


Why are you doing this?
We want to increase the reliability, stability, and speed of the LLVN services. 
The current machine is outdated and is not set up for our current needs. 

If you have any questions, please do not hesitate to ask.

Thank you,
Tanya___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] Prebuilt binary for Windows

[Zachary Turner via lldb-dev]

I will commit it, in the meantime can you request commit access so that any
future patches you can commit?

On Wed, Jan 4, 2017 at 1:54 PM Vadim Chugunov  wrote:

> Thanks!
>
> Would anyone be so kind to commit that?
>
> On Wed, Jan 4, 2017 at 11:47 AM, Zachary Turner 
> wrote:
>
> Sorry, a combination of national holidays and extended vacations happened
> and this fell off my radar.  lgtm
>
> On Wed, Jan 4, 2017 at 11:46 AM Vadim Chugunov  wrote:
>
> Zachary,
> Can you please take a look at that change? (
> https://reviews.llvm.org/D27476)
>
> It'll be sad if another snapshot build gets published with broken lldb. :(
>
>
> On Tue, Dec 6, 2016 at 11:54 AM, Vadim Chugunov  wrote:
>
> This seems to work: https://reviews.llvm.org/D27476
>
> On Mon, Dec 5, 2016 at 12:04 PM, Hans Wennborg  wrote:
>
> The only thing needed to build the installer should be having NSIS
> installed and building the "package" target generated by CMake. The
> other prerequisites are mostly for building the visual studio
> clang-format plugin.
>
> Having said that, you don't even have to build the installer to see
> what goes in it. Just building the "install" target generated by CMake
> will install the same set of files.
>
> I'm not sure how LLDB's cmake files are organized, but in the end
> what's required is invoking the install() command:
> https://cmake.org/cmake/help/v3.0/command/install.html  In LLVM, this
> is done automatically by macros such as add_llvm_executale, etc.
>
> On Mon, Dec 5, 2016 at 11:56 AM, Vadim Chugunov  wrote:
> > Hi Hans,
> >
> > I'd love to help, but I don't have half the tools that
> > build_llvm_package.bat requires installed on my machine.  My setup is to
> > build llvm with msbuild.   Is it possible to build the installer this way
> > too?
> >
> > Can you point me to the specific CMake source that determines what's
> > included in the package?   At a glance, everything from
> > %LLVM%/lib/site-packages is missing.
> >
> > Vadim
> >
> > On Mon, Dec 5, 2016 at 10:41 AM, Hans Wennborg 
> wrote:
> >>
> >> Is anyone working on this?
> >>
> >> I'm happy to include LLDB in the installer, but I'm really not the
> >> best person to be debugging it.
> >>
> >> If more files need to be included in the install, that's configured in
> >> the CMake files (what's installed by the 'install' build target is
> >> also what ends up going into the installer). If it needs more build
> >> flags, patches to build_llvm_package.bat are welsome.
> >
> >
> >
>
>
>
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] LLVM Social - Paris: January 17th, 2017

[Arnaud Allard de Grandmaison via lldb-dev]

The next LLVM social in Paris will happen on January 17, 2017.

Everyone interested in LLVM, Clang, lldb, Polly, lld, ... is invited to
join.

This time, we will have a talk from Michael Kruze: "*Where to put Polly ?
Interactions between Polly and LLVM's other passes.*"

Polly is an extension for LLVM for polyhedral optimization. Unfortunately
what transformations it can perform depends on the form of the IR. Some
LLVM passes improve the analyzability for Polly, but others reduce
optimization opportunities. What would be the ideal pass pipeline for Polly
?
Event details, including registration (free but mandatory) at
http://www.meetup.com/LLVM-Clang-social

Looking forward to meet you,
-- Arnaud de Grandmaison, Duncan Sands, Sylvestre Ledru
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] Cross compile for iphone

[jichao yang via lldb-dev]

Hi, is it possible to cross compile lldb for iphone?

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

[lldb-dev] [4.0.0 Release] One week to the branch

[Hans Wennborg via lldb-dev]

This is just a quick reminder that branching for the upcoming release
is scheduled for one week from now, 12 January 2017. Please try to
avoid disruptive changes right before the branch.

The full schedule was posted in a previous email [1] and also under
"Upcoming Releases" on http://llvm.org/

Note that when the branch happens, the trunk version will become 5.0.0
as per the new versioning scheme [2].

Cheers,
Hans

 [1] http://lists.llvm.org/pipermail/llvm-dev/2016-December/107805.html
 [2] http://blog.llvm.org/2016/12/llvms-new-versioning-scheme.html
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev