Re: [lldb-dev] [3.8 Release] Schedule and call for testers

[Daniel Sanders via lldb-dev]

Sounds good to me. I'll do the usual mips packages.

> -Original Message-
> From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf
> Of Hans Wennborg
> Sent: 11 December 2015 23:15
> To: llvm-dev; cfe-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org
> Cc: Dimitry Andric; Sebastian Dreßler; Renato Golin; Pavel Labath; Sylvestre
> Ledru; Ed Maste; Ben Pope; Daniel Sanders; Nikola Smiljanić; Brian Cain; Tom
> Stellard
> Subject: [3.8 Release] Schedule and call for testers
> 
> Dear everyone,
> 
> It's not quite time to start the 3.8 release process, but it's time to
> start planning.
> 
> Please let me know if you want to help with testing and building
> release binaries for your favourite platform. (If you were a tester on
> the previous release, you're cc'd on this email.)
> 
> I propose the following schedule for the 3.8 release:
> 
> - 13 January: Create 3.8 branch. Testing Phase 1: RC1 binaries built
> and tested, bugs fixed. Any almost-complete features need to be
> wrapped up or disabled on the branch ASAP, and definitely before this
> phase ends.
> 
> - 27 January: Testing Phase 2: RC2 binaries built and tested. Only
> critical bug fixes from now on. Further RCs published as we approach..
> 
> - 18 February: Cut the final release, build binaries, ship when ready.
> 
> Unless there are any objections, I'll post this on the web page.
> 
> Cheers,
> Hans
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [3.8 Release] We have branched

[Daniel Sanders via lldb-dev]

Hi Hans,

I tried the release branch last night and I'm having problems building it. The 
problem is that test-suite is now building as part of the Phase[123] builds 
(because this project contains CMakeLists.txt's now) but cmake 3.0.2 (from 
Debian Jessie) generates an invalid Makefile.
The error is:
CMakeFiles/test-suite.dir/build.make:112: *** target pattern contains 
no '%'.  Stop.
CMakeFiles/Makefile2:199: recipe for target 
'CMakeFiles/test-suite.dir/all' failed
And the referenced line of the generated makefile is:
test-suite-stamps/test-suite-force-rebuild: 
/home/das-local/llvm-release-3.8/release/branches_release_38/llvm.src/$
it looks like cmake isn't fully expanding its generator expressions.

Looking at my logs, it looks like the test-suite used to configure in 3.6.2 but 
didn't build as part of test-release.sh and then 3.7.0 stopped since we had 
switched to cmake and there was no CMakeLists.txt.
I've always run the test-suite as a separate step as described in 
http://llvm.org/docs/ReleaseProcess.html. Should we stop creating the 
projects/test-suite symlink to get back to the behaviour from 3.7.0 or should 
we do something else?

> -Original Message-
> From: cfe-dev [mailto:cfe-dev-boun...@lists.llvm.org] On Behalf Of Hans
> Wennborg via cfe-dev
> Sent: 13 January 2016 18:21
> To: llvm-dev; cfe-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org
> Subject: [cfe-dev] [3.8 Release] We have branched
> 
> And so the release process begins.
> 
> The 3.8 branch was created today from trunk at r257626, and the trunk
> version was then bumped to 3.9.
> 
> Release blockers are tracked by http://llvm.org/PR26059. If you find
> any bugs (either new or already in the tracker) that you think need to
> be fixed before the release, please mark them as blocking this bug.
> 
> To get a change committed on the branch, first commit it to trunk as
> usual, then reply to the commit message on the mailing list with
> myself and the appropriate code owner CC'd, asking for the change to
> be merged to the branch.
> 
> Release notes for 3.8 should be committed directly to the branch, or
> sent to me in an email and I'll do it for you. If you made any
> non-trivial changes in the last six months (or know someone else who
> did), please make sure they get mentioned in the notes.
> 
> Next up on the schedule is preparing the first release candidate
> (RC1). This will happen in a few days, once the branch is known to be
> in good shape.
> 
> The hardest part of releasing is staying on top of everything. Please
> help me out by CC'ing me on any bugs, commits, or other issues that
> are relevant for the release. If I'm not CC'd, there's a large chance
> I will miss it.
> 
> Cheers,
> Hans
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [3.8 Release] We have branched

[Daniel Sanders via lldb-dev]

> -Original Message-
> From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf
> Of Hans Wennborg
> Sent: 15 January 2016 15:52
> To: Daniel Sanders
> Cc: llvm-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org; cfe-
> d...@lists.llvm.org
> Subject: Re: [cfe-dev] [3.8 Release] We have branched
> 
> Hi Daniel,
> 
> Thanks for trying out the branch :-)
> 
> On Fri, Jan 15, 2016 at 5:30 AM, Daniel Sanders
>  wrote:
> > Hi Hans,
> >
> > I tried the release branch last night and I'm having problems building it. 
> > The
> problem is that test-suite is now building as part of the Phase[123] builds
> (because this project contains CMakeLists.txt's now) but cmake 3.0.2 (from
> Debian Jessie) generates an invalid Makefile.
> > The error is:
> > CMakeFiles/test-suite.dir/build.make:112: *** target pattern 
> > contains
> no '%'.  Stop.
> > CMakeFiles/Makefile2:199: recipe for target 'CMakeFiles/test-
> suite.dir/all' failed
> > And the referenced line of the generated makefile is:
> > test-suite-stamps/test-suite-force-rebuild: /home/das-local/llvm-
> release-3.8/release/branches_release_38/llvm.src/$
> > it looks like cmake isn't fully expanding its generator expressions.
> >
> > Looking at my logs, it looks like the test-suite used to configure in 3.6.2 
> > but
> didn't build as part of test-release.sh and then 3.7.0 stopped since we had
> switched to cmake and there was no CMakeLists.txt.
> > I've always run the test-suite as a separate step as described in
> http://llvm.org/docs/ReleaseProcess.html. Should we stop creating the
> projects/test-suite symlink to get back to the behaviour from 3.7.0 or should
> we do something else?
> 
> Yes, I made the script stop making the symlink in r257791 and merged
> it to the branch. Did that not work for you, or were you at an earlier
> revision?
> 
> Thanks,
> Hans

I'm at r257773 so it looks like I didn't pick up that change. I'll give it 
another try tonight.

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

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

[Daniel Sanders via lldb-dev]

This isn't rc1 but the tip of the release branch had some X86 test failures on 
my most recent build:
Failing Tests (24):
libc++ :: 
std/input.output/file.streams/fstreams/filebuf.virtuals/overflow.pass.cpp
libc++ :: 
std/input.output/file.streams/fstreams/filebuf.virtuals/underflow.pass.cpp
libc++ :: std/input.output/iostream.format/ext.manip/get_time.pass.cpp
libc++ :: std/input.output/iostream.format/ext.manip/put_time.pass.cpp
libc++ :: 
std/input.output/iostreams.base/ios.base/ios.base.callback/register_callback.pass.cpp
libc++ :: 
std/input.output/iostreams.base/ios.base/ios.base.locales/imbue.pass.cpp
libc++ :: 
std/input.output/iostreams.base/ios/basic.ios.members/imbue.pass.cpp
libc++ :: 
std/input.output/stream.buffers/streambuf/streambuf.cons/copy.pass.cpp
libc++ :: 
std/input.output/stream.buffers/streambuf/streambuf.cons/default.pass.cpp
libc++ :: 
std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.assign/assign.pass.cpp
libc++ :: 
std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.assign/swap.pass.cpp
libc++ :: 
std/localization/locale.categories/category.collate/locale.collate.byname/hash.pass.cpp
libc++ :: 
std/localization/locale.categories/category.collate/locale.collate.byname/types.pass.cpp
libc++ :: 
std/localization/locale.categories/category.ctype/locale.codecvt.byname/ctor_wchar_t.pass.cpp
libc++ :: 
std/localization/locale.categories/category.ctype/locale.ctype.byname/types.pass.cpp
libc++ :: std/localization/locales/locale/locale.cons/default.pass.cpp
libc++ :: std/localization/locales/locale/locale.members/name.pass.cpp
libc++ :: std/localization/locales/locale/locale.operators/eq.pass.cpp
libc++ :: std/localization/locales/locale/locale.statics/global.pass.cpp
libc++ :: std/re/re.regex/re.regex.locale/imbue.pass.cpp
libc++ :: std/re/re.traits/default.pass.cpp
libc++ :: std/re/re.traits/getloc.pass.cpp
libc++ :: std/re/re.traits/imbue.pass.cpp
libomp :: barrier/omp_barrier.c

Big-endian mips gave this during phase 3:
CMake Error at cmake/modules/HandleLLVMOptions.cmake:43 (message):
  Host Clang must be able to find libstdc++4.7 or newer!
It's possible that this is a machine config issue. We moved offices over the 
weekend (just across the street) and my normal machine somehow lost the ability 
to boot in the process. I'm borrowing a replacement at the moment.

Little-endian mips is just about to finish Phase 2 so I'll know if it's a more 
general problem soon.

> -Original Message-
> From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf
> Of Hans Wennborg
> Sent: 19 January 2016 23:56
> To: Ben Pope; Dimitry Andric; Daniel Sanders; Nikola Smiljanić; Brian Cain;
> Renato Golin; Sylvestre Ledru
> Cc: cfe-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org; llvm-dev
> Subject: Re: [3.8 Release] RC1 has been tagged
> 
> (cc'ing non-legacy llvm-dev this time; apologies if you get this
> twice. Please don't reply-all to the first one.)
> 
> On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg 
> wrote:
> > Dear testers,
> >
> > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
> > r258223. (It took a little longer than I'd planned, sorry about that.)
> >
> > There are still a bunch of open merge requests and bug reports, but I
> > wanted to get the tag in so we can see what the build and test status
> > are on the various platforms.
> >
> > I verified that it currently builds and tests cleanly for me on x86_64
> > Linux, Mac OS X* and Windows.
> >
> > Please build, test, and upload binaries to the sftp. Let me know if how it
> goes.
> >
> > Thanks,
> > Hans
> >
> >
> > [*] For Mac, I had to set CFLAGS="-isysroot `xcrun -show-sdk-path`"
> > CXXFLAGS="-isysroot `xcrun -show-sdk-path`" for the build to work,
> > otherwise stage-2 Clang couldn't find the SDK. I don't remember if I
> > had to do this last time; maybe some upgrade changed something.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [cfe-dev] [3.8 Release] We have branched

[Daniel Sanders via lldb-dev]

Sorry for not replying back on this thread. We moved offices over the weekend 
and I've been busy sorting various things out.

I'm currently building rc1 but my most recent build on the release branch had 
some regressions. I mentioned them on the rc1 thread but to summarize here:
* X86 failed ~20 libc++ tests and 1 libomp test
* Big-endian mips fails to configure phase 3. It reports errors about being 
unable to find libstdc++4.7 or newer. I've just resurrected the machine that 
normally does this build (it died during the move) so I'll start rc1 on it 
finishes the buildbot builds that have accumulated.
* Little-endian mips is still building (I had to move the machine and restart 
the build) but it's got further than big-endian.

> -Original Message-
> From: Renato Golin [mailto:renato.go...@linaro.org]
> Sent: 20 January 2016 15:33
> To: Daniel Sanders
> Cc: Hans Wennborg; llvm-dev; cfe-...@lists.llvm.org; openmp-
> d...@lists.llvm.org; lldb-dev@lists.llvm.org
> Subject: Re: [llvm-dev] [cfe-dev] [3.8 Release] We have branched
> 
> Hans, Daniel,
> 
> How are things going? It's been 5 days and no word. I'm running the
> tests now, just in case, but would be good to know that no one would
> be committing to the release candidate 1 tree in the mean time.
> 
> cheers,
> --renato
> 
> On 15 January 2016 at 15:56, Daniel Sanders via llvm-dev
>  wrote:
> >> -Original Message-
> >> From: hwennb...@google.com [mailto:hwennb...@google.com] On
> Behalf
> >> Of Hans Wennborg
> >> Sent: 15 January 2016 15:52
> >> To: Daniel Sanders
> >> Cc: llvm-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org; cfe-
> >> d...@lists.llvm.org
> >> Subject: Re: [cfe-dev] [3.8 Release] We have branched
> >>
> >> Hi Daniel,
> >>
> >> Thanks for trying out the branch :-)
> >>
> >> On Fri, Jan 15, 2016 at 5:30 AM, Daniel Sanders
> >>  wrote:
> >> > Hi Hans,
> >> >
> >> > I tried the release branch last night and I'm having problems building 
> >> > it.
> The
> >> problem is that test-suite is now building as part of the Phase[123] builds
> >> (because this project contains CMakeLists.txt's now) but cmake 3.0.2
> (from
> >> Debian Jessie) generates an invalid Makefile.
> >> > The error is:
> >> > CMakeFiles/test-suite.dir/build.make:112: *** target pattern
> contains
> >> no '%'.  Stop.
> >> > CMakeFiles/Makefile2:199: recipe for target 'CMakeFiles/test-
> >> suite.dir/all' failed
> >> > And the referenced line of the generated makefile is:
> >> > test-suite-stamps/test-suite-force-rebuild: /home/das-local/llvm-
> >> release-
> 3.8/release/branches_release_38/llvm.src/$
> >> > it looks like cmake isn't fully expanding its generator expressions.
> >> >
> >> > Looking at my logs, it looks like the test-suite used to configure in 
> >> > 3.6.2
> but
> >> didn't build as part of test-release.sh and then 3.7.0 stopped since we had
> >> switched to cmake and there was no CMakeLists.txt.
> >> > I've always run the test-suite as a separate step as described in
> >> http://llvm.org/docs/ReleaseProcess.html. Should we stop creating the
> >> projects/test-suite symlink to get back to the behaviour from 3.7.0 or
> should
> >> we do something else?
> >>
> >> Yes, I made the script stop making the symlink in r257791 and merged
> >> it to the branch. Did that not work for you, or were you at an earlier
> >> revision?
> >>
> >> Thanks,
> >> Hans
> >
> > I'm at r257773 so it looks like I didn't pick up that change. I'll give it 
> > another
> try tonight.
> >
> > Thanks
> > ___
> > LLVM Developers mailing list
> > llvm-...@lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

[Daniel Sanders via lldb-dev]

I still haven't built rc1 yet but I've found the cause of most (if not all) of 
the libc++ failures. This system does not have the en_US.UTF-8 locale.

I'm currently putting a patch together to add appropriate REQUIRES lines to 
tests that require en_US.UTF-8. Once I've done that and committed it, I'm going 
to enable this locale along with the others that lit is complaining about 
(fr_FR.UTF-8, ru_RU.UTF-8, zh_CN.UTF-*, fr_CA.ISO8859-1, and cs_CZ.ISO8859-2).

> -Original Message-
> From: cfe-dev [mailto:cfe-dev-boun...@lists.llvm.org] On Behalf Of Daniel
> Sanders via cfe-dev
> Sent: 20 January 2016 10:30
> To: Hans Wennborg; Ben Pope; Dimitry Andric; Nikola Smiljanić; Brian Cain;
> Renato Golin; Sylvestre Ledru
> Cc: llvm-dev; cfe-dev; openmp-...@lists.llvm.org; lldb-dev@lists.llvm.org
> Subject: Re: [cfe-dev] [3.8 Release] RC1 has been tagged
> 
> This isn't rc1 but the tip of the release branch had some X86 test failures on
> my most recent build:
> Failing Tests (24):
> libc++ ::
> std/input.output/file.streams/fstreams/filebuf.virtuals/overflow.pass.cpp
> libc++ ::
> std/input.output/file.streams/fstreams/filebuf.virtuals/underflow.pass.cpp
> libc++ :: std/input.output/iostream.format/ext.manip/get_time.pass.cpp
> libc++ :: std/input.output/iostream.format/ext.manip/put_time.pass.cpp
> libc++ ::
> std/input.output/iostreams.base/ios.base/ios.base.callback/register_callbac
> k.pass.cpp
> libc++ ::
> std/input.output/iostreams.base/ios.base/ios.base.locales/imbue.pass.cpp
> libc++ ::
> std/input.output/iostreams.base/ios/basic.ios.members/imbue.pass.cpp
> libc++ ::
> std/input.output/stream.buffers/streambuf/streambuf.cons/copy.pass.cpp
> libc++ ::
> std/input.output/stream.buffers/streambuf/streambuf.cons/default.pass.c
> pp
> libc++ ::
> std/input.output/stream.buffers/streambuf/streambuf.protected/streamb
> uf.assign/assign.pass.cpp
> libc++ ::
> std/input.output/stream.buffers/streambuf/streambuf.protected/streamb
> uf.assign/swap.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.collate/locale.collate.byname/has
> h.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.collate/locale.collate.byname/typ
> es.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.ctype/locale.codecvt.byname/cto
> r_wchar_t.pass.cpp
> libc++ ::
> std/localization/locale.categories/category.ctype/locale.ctype.byname/types
> .pass.cpp
> libc++ :: std/localization/locales/locale/locale.cons/default.pass.cpp
> libc++ :: std/localization/locales/locale/locale.members/name.pass.cpp
> libc++ :: std/localization/locales/locale/locale.operators/eq.pass.cpp
> libc++ :: std/localization/locales/locale/locale.statics/global.pass.cpp
> libc++ :: std/re/re.regex/re.regex.locale/imbue.pass.cpp
> libc++ :: std/re/re.traits/default.pass.cpp
> libc++ :: std/re/re.traits/getloc.pass.cpp
> libc++ :: std/re/re.traits/imbue.pass.cpp
> libomp :: barrier/omp_barrier.c
> 
> Big-endian mips gave this during phase 3:
>   CMake Error at cmake/modules/HandleLLVMOptions.cmake:43
> (message):
> Host Clang must be able to find libstdc++4.7 or newer!
> It's possible that this is a machine config issue. We moved offices over the
> weekend (just across the street) and my normal machine somehow lost the
> ability to boot in the process. I'm borrowing a replacement at the moment.
> 
> Little-endian mips is just about to finish Phase 2 so I'll know if it's a more
> general problem soon.
> 
> > -Original Message-
> > From: hwennb...@google.com [mailto:hwennb...@google.com] On
> Behalf
> > Of Hans Wennborg
> > Sent: 19 January 2016 23:56
> > To: Ben Pope; Dimitry Andric; Daniel Sanders; Nikola Smiljanić; Brian Cain;
> > Renato Golin; Sylvestre Ledru
> > Cc: cfe-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org; llvm-dev
> > Subject: Re: [3.8 Release] RC1 has been tagged
> >
> > (cc'ing non-legacy llvm-dev this time; apologies if you get this
> > twice. Please don't reply-all to the first one.)
> >
> > On Tue, Jan 19, 2016 at 3:47 PM, Hans Wennborg 
> > wrote:
> > > Dear testers,
> > >
> > > Start your engines; 3.8.0-rc1 was just tagged from the 3.8 branch at
> > > r258223. (It took a little longer than I'd planned, sorry about that.)
> > >
> > > There are still a bunch of open merge requests and bug reports, but I
> > > wanted to get the tag in so we can see what the build and test status
> > > are on the various platforms.
> > >
> > > I verified that it currently builds and tests cleanly for me on x86_64
> > > Linux, Mac OS X* and Windows.
> > >
> > > Please build, test, and upload binaries to the sftp. Let me know if how it
> > goes.
> > >
> > > Thanks,
> > > Hans
> > >
> > >
> > > [*] For Mac, I had to set CFLAGS="-isysroot `xcrun -show-sdk-path`"
> > > CXXFLAGS="-isysroot `xcrun -show-sdk-path`" for the build to work,
> > > otherwise stage-2 Clang couldn't find the SDK. I don't remem

Re: [lldb-dev] [3.8 Release] RC1 has been tagged

[Daniel Sanders via lldb-dev]

I have some proper rc1 results now.

clang+llvm-3.8.0-rc1-mips-linux-gnu.tar.xz
test-release.sh refused to run 'make check-all' because libcxx_tsan 
failed to configure. This is because the thread sanitizer is not supported on 
MIPS32.
After working around this (patch will follow shortly):
~200 sanitizer failures. Most of them tsan (which as noted 
above shouldn't be running), but other sanitizers too.
lots of libc++ failures split into two cases:
(No ticket yet) - Missing builtins for 64-bit atomics. 
Vasileios Kalintiris has given me a patch that should fix this
PR26277 - Some diagnostic checking tests fail because the 
assembler can't find it's input file. Clang didn't create it due to frontend 
errors but still called GAS.

clang+llvm-3.8.0-rc1-mipsel-linux-gnu.tar.xz
lots of libc++ failures split into two cases:
(No ticket yet) - Missing builtins for 64-bit atomics. 
Vasileios Kalintiris has given me a patch that should fix this
PR26277 - Some diagnostic checking tests fail because the 
assembler can't find it's input file. Clang didn't create it due to frontend 
errors but still called GAS.
Test-suite was ok.

clang+llvm-3.8.0-rc1-x86_64-linux-gnu-debian8.tar.xz (native X86_64)
PR26252 - libc++ fails 23 tests due to missing en_US-UTF8 locale. I 
have two patches in progress for this and I've also made the problem go away by 
enabling this locale.
PR26253 - libomp fails runtime/test/barrier/omp_barrier.c
Test-suite was ok

clang+llvm-3.8.0-rc1-x86_64-linux-gnu-debian8.tar.xz (cross compiling to Mips)
10/23 test-suite configs ok. The rest are still running.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

[Daniel Sanders via lldb-dev]

> Have you accidentally checked out the test-suite into /projects? if it's 
> there it will auto-configure

We fixed it for rc1 but test-release.sh used to put the test-suite there.

From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of James 
Molloy via llvm-dev
Sent: 26 January 2016 16:05
To: Ismail Donmez; Nikola Smiljanic
Cc: Ben Pope; llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB 
Dev
Subject: Re: [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

The test-suite shouldn't be being build with CMake for the release - the CMake 
system is not yet ready. Have you accidentally checked out the test-suite into 
/projects? if it's there it will auto-configure.

James

On Tue, 26 Jan 2016 at 16:01 Ismail Donmez via cfe-dev 
mailto:cfe-...@lists.llvm.org>> wrote:
On Tue, Jan 26, 2016 at 1:56 PM, Nikola Smiljanic via llvm-dev
mailto:llvm-...@lists.llvm.org>> wrote:
> Phase1 fails to build on openSUSE 13.2, can anyone see what's wrong from
> this log file?

Something wrong with the test-suite:

make -f CMakeFiles/test-suite.dir/build.make CMakeFiles/test-suite.dir/depend
make[2]: Entering directory
'/home/nikola/rc1/Phase1/Release/llvmCore-3.8.0-rc1.obj'
CMakeFiles/test-suite.dir/build.make:112: *** target pattern contains
no '%'.  Stop.
make[2]: Leaving directory
'/home/nikola/rc1/Phase1/Release/llvmCore-3.8.0-rc1.obj'
CMakeFiles/Makefile2:198: recipe for target
'CMakeFiles/test-suite.dir/all' failed
make[1]: *** [CMakeFiles/test-suite.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs
___
cfe-dev mailing list
cfe-...@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

[Daniel Sanders via lldb-dev]

I've been putting together a patch to bring that back and I've just posted it 
as http://reviews.llvm.org/D16679.

From: Nikola Smiljanic [mailto:popiz...@gmail.com]
Sent: 28 January 2016 02:00
To: Daniel Sanders
Cc: James Molloy; Ismail Donmez; Ben Pope; cfe-dev; openmp-dev 
(openmp-...@lists.llvm.org); LLDB Dev
Subject: Re: [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

It seems that test-release was fixed, thanks everyone. Builds are OK but I'd 
like to know where did test-suite go? All I see is the llvm.src directory, am I 
supposed to export test-suite myself?

On Wed, Jan 27, 2016 at 9:47 PM, Daniel Sanders 
mailto:daniel.sand...@imgtec.com>> wrote:
> Have you accidentally checked out the test-suite into /projects? if it's 
> there it will auto-configure

We fixed it for rc1 but test-release.sh used to put the test-suite there.

From: llvm-dev 
[mailto:llvm-dev-boun...@lists.llvm.org]
 On Behalf Of James Molloy via llvm-dev
Sent: 26 January 2016 16:05
To: Ismail Donmez; Nikola Smiljanic
Cc: Ben Pope; llvm-dev; cfe-dev; openmp-dev 
(openmp-...@lists.llvm.org); LLDB Dev
Subject: Re: [llvm-dev] [cfe-dev] [3.8 Release] RC1 has been tagged

The test-suite shouldn't be being build with CMake for the release - the CMake 
system is not yet ready. Have you accidentally checked out the test-suite into 
/projects? if it's there it will auto-configure.

James

On Tue, 26 Jan 2016 at 16:01 Ismail Donmez via cfe-dev 
mailto:cfe-...@lists.llvm.org>> wrote:
On Tue, Jan 26, 2016 at 1:56 PM, Nikola Smiljanic via llvm-dev
mailto:llvm-...@lists.llvm.org>> wrote:
> Phase1 fails to build on openSUSE 13.2, can anyone see what's wrong from
> this log file?

Something wrong with the test-suite:

make -f CMakeFiles/test-suite.dir/build.make CMakeFiles/test-suite.dir/depend
make[2]: Entering directory
'/home/nikola/rc1/Phase1/Release/llvmCore-3.8.0-rc1.obj'
CMakeFiles/test-suite.dir/build.make:112: *** target pattern contains
no '%'.  Stop.
make[2]: Leaving directory
'/home/nikola/rc1/Phase1/Release/llvmCore-3.8.0-rc1.obj'
CMakeFiles/Makefile2:198: recipe for target
'CMakeFiles/test-suite.dir/all' failed
make[1]: *** [CMakeFiles/test-suite.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs
___
cfe-dev mailing list
cfe-...@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

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

Re: [lldb-dev] [3.8 Release] RC2 has been tagged

[Daniel Sanders via lldb-dev]

Here's the status for my builds so far.

clang+llvm-3.8.0-rc2-x86_64-linux-gnu-debian8.tar.xz (sha1sum: 
2b546efa5bab19d6711771ef31711d07b4a3f23f)
Native:
All ok
Cross compiling to various MIPS targets:
16 out of 23 configs passed
1 out of the remaining 7 failed a small number of tests with a 
timeout. I expect these will pass when I re-run them.
Remaining 6 configs still running...

clang+llvm-3.8.0-rc2-mips-linux-gnu.tar.xz (sha1sum: 
b46221e1bb54255e9e060f06bb72bb2ba630ff15)
Failed to run check-all due to tsan'd libc++ build failing
PR26278 - My fix for this was committed just after the rc2 tag 
so in order to get some check-all results, I applied those four patches 
(r25966[1456]) and re-ran check-all.
PR26369 - Several failures related to the lack of -latomic 
which is needed for 64-bit atomics.
PR26476 - One new failure in libc++ (I probably just missed it 
amongst the others). Apparently std::regex_traits says that '-' doesn't belong 
to the 'w' class but only on big-endian.
check-all appears to hang at 99%. I'll look into this.
LNT (using the clean rc2)
1 of 3 passed successfully, the other two are still running

clang+llvm-3.8.0-rc2-mipsel-linux-gnu.tar.xz (sha1sum: 
9f89cccfdb5cf6a27138b84a631003c4a04f456d)
Build almost ok. I only have failures related to PR26369.
LNT just started.

> -Original Message-
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Hans
> Wennborg via lldb-dev
> Sent: 02 February 2016 21:16
> To: release-test...@lists.llvm.org
> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev
> Subject: [lldb-dev] [3.8 Release] RC2 has been tagged
> 
> Dear testers,
> 
> Release Candidate 2 has just been tagged [1]. Please build, test, and
> upload to the sftp.
> 
> I know there are still outstanding issues from RC1, but there have
> been a lot of merges going into the branch and I think it's time for
> another round of RC testing.
> 
> This RC comes a little behind schedule, sorry about that, but I'm
> still optimistic about hitting the target of releasing towards the end
> of February.
> 
> Thanks for all the work you've put into this release so far!
> 
> Hans
> 
>  [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-
> February/009739.html
> ___
> 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] [3.8 Release] RC2 has been tagged

[Daniel Sanders via lldb-dev]

Here's a quick update
> clang+llvm-3.8.0-rc2-x86_64-linux-gnu-debian8.tar.xz (sha1sum:
> 2b546efa5bab19d6711771ef31711d07b4a3f23f)
>   Native:
>   All ok
>   Cross compiling to various MIPS targets:
>   16 out of 23 configs passed
>   1 out of the remaining 7 failed a small number of tests with a
> timeout. I expect these will pass when I re-run them.
>   Remaining 6 configs still running...

For cross-compilation, it's now 22 out of 23 passing. The remaining config had 
fewer timeouts on the re-run but not all of them went away. I'm re-running the 
last two timeouts while my machine is less busy.
 
> clang+llvm-3.8.0-rc2-mips-linux-gnu.tar.xz (sha1sum:
> b46221e1bb54255e9e060f06bb72bb2ba630ff15)
>   Failed to run check-all due to tsan'd libc++ build failing
>   PR26278 - My fix for this was committed just after the rc2 tag
> so in order to get some check-all results, I applied those four patches
> (r25966[1456]) and re-ran check-all.
>   PR26369 - Several failures related to the lack of -latomic
> which is needed for 64-bit atomics.
>   PR26476 - One new failure in libc++ (I probably just missed it
> amongst the others). Apparently std::regex_traits says that '-' doesn't belong
> to the 'w' class but only on big-endian.
>   check-all appears to hang at 99%. I'll look into this.
>   LNT (using the clean rc2)
>   1 of 3 passed successfully, the other two are still running

LNT finished successfully and everything passed.

I've identified the hanging test. It's a mips64 msan test so I'm planning to 
mark it UNSUPPORTED (XFAIL will still hang) since this isn't a regression on 
the last release.

We're still investigating PR26476, and we're also trying to get PR26369 
committed+merged.

 > clang+llvm-3.8.0-rc2-mipsel-linux-gnu.tar.xz (sha1sum:
> 9f89cccfdb5cf6a27138b84a631003c4a04f456d)
>   Build almost ok. I only have failures related to PR26369.
>   LNT just started.

All ok aside from PR26369.

> > -Original Message-
> > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Hans
> > Wennborg via lldb-dev
> > Sent: 02 February 2016 21:16
> > To: release-test...@lists.llvm.org
> > Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB
> Dev
> > Subject: [lldb-dev] [3.8 Release] RC2 has been tagged
> >
> > Dear testers,
> >
> > Release Candidate 2 has just been tagged [1]. Please build, test, and
> > upload to the sftp.
> >
> > I know there are still outstanding issues from RC1, but there have
> > been a lot of merges going into the branch and I think it's time for
> > another round of RC testing.
> >
> > This RC comes a little behind schedule, sorry about that, but I'm
> > still optimistic about hitting the target of releasing towards the end
> > of February.
> >
> > Thanks for all the work you've put into this release so far!
> >
> > Hans
> >
> >  [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-
> > February/009739.html
> > ___
> > 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] [3.8 Release] Release status

[Daniel Sanders via lldb-dev]

Hi Hans,

I think PR26369 should be on the list but we could potentially make do without 
it (see below). Without it we get 23 failures on libcxx tests caused by failing 
to link the tests with libatomic but libcxx itself is fine.

One thing that's unclear is whether these failures are really regressions or 
not. My logs for 3.7.1 don't show any failures which would suggest they are 
regressions. However I've just run 'make check-libcxx' on that old build and I 
get the same failures I see on 3.8. I'm currently digging into the 3.7.1 build 
to see if I can explain why the log differs from what I currently get.

From: lldb-dev [lldb-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg via 
lldb-dev [lldb-dev@lists.llvm.org]
Sent: 19 February 2016 00:22
To: llvm-dev; cfe-dev; LLDB Dev; openmp-dev (openmp-...@lists.llvm.org); 
release-test...@lists.llvm.org; Cong Hou; Davide Italiano; Quentin Colombet; 
Hal Finkel; Chandler Carruth; JF Bastien; Nemanja Ivanovic; Matthias Braun
Subject: [lldb-dev] [3.8 Release] Release status

According to the schedule (e.g. on the right on llvm.org), we should
have tagged the release by now, but we haven't, so we're officially
behind schedule. I'm still optimistic that we can wrap this up pretty
soon, though.

This is what's blocking us:

- PR26509: Crash in InnerLoopVectorizer::vectorizeLoop()
  I'm waiting to hear what Cong comes up with, otherwise we can revert
r255691 on the branch

- Shrink-wrapping vs TLS: Davide and Quentin are working on it

- PR26600: Loop vectorization creates an unsafe out-of-bounds load
  There's a patch out: http://reviews.llvm.org/D17332
  But no comments yet.. Hal?

- PR26564: Performance regression in AA
  Patch in review, but it makes me a little uneasy since it's big and
requires pulling in some refactoring patches too :-/

- ARM: fix VFP asm constraints: http://reviews.llvm.org/D17349
  It's not a regression, but I'll take it if it lands real soon.

- PR26500: shrink-wrapping vs PPC
  Patch in review: http://reviews.llvm.org/D17294
  Looks like it's moving along.

- PR26081: Assertion failed: (BitWidth == RHS.BitWidth && ...
  I believe Matthias is working on it?
  Will revert r252839 to unblock otherwise.

- PR26485: regression lowering TLS access in C on Darwin
  Is no one looking? :-(

If you're on one of these bugs or code reviews, etc., please try to
prioritize them if you can.

Also, please let me know if my list is missing something.

Cheers,
Hans
___
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] [3.8 Release] Release status

[Daniel Sanders via lldb-dev]

I've changed the lit arguments to '-v' on my old 3.7.1 build and re-run 
check-all. I can confirm that these failures aren't regressions since LLVM 
3.7.1 did not actually run any libc++ tests. Looking through the generated 
makefiles it seems that check-libcxx wasn't part of check-all.

From: Daniel Sanders
Sent: 19 February 2016 14:33
To: Hans Wennborg; llvm-dev; cfe-dev; LLDB Dev; openmp-dev 
(openmp-...@lists.llvm.org); release-test...@lists.llvm.org; Cong Hou; Davide 
Italiano; Quentin Colombet; Hal Finkel; Chandler Carruth; JF Bastien; Nemanja 
Ivanovic; Matthias Braun
Subject: RE: [lldb-dev] [3.8 Release] Release status

Hi Hans,

I think PR26369 should be on the list but we could potentially make do without 
it (see below). Without it we get 23 failures on libcxx tests caused by failing 
to link the tests with libatomic but libcxx itself is fine.

One thing that's unclear is whether these failures are really regressions or 
not. My logs for 3.7.1 don't show any failures which would suggest they are 
regressions. However I've just run 'make check-libcxx' on that old build and I 
get the same failures I see on 3.8. I'm currently digging into the 3.7.1 build 
to see if I can explain why the log differs from what I currently get.

From: lldb-dev [lldb-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg via 
lldb-dev [lldb-dev@lists.llvm.org]
Sent: 19 February 2016 00:22
To: llvm-dev; cfe-dev; LLDB Dev; openmp-dev (openmp-...@lists.llvm.org); 
release-test...@lists.llvm.org; Cong Hou; Davide Italiano; Quentin Colombet; 
Hal Finkel; Chandler Carruth; JF Bastien; Nemanja Ivanovic; Matthias Braun
Subject: [lldb-dev] [3.8 Release] Release status

According to the schedule (e.g. on the right on llvm.org), we should
have tagged the release by now, but we haven't, so we're officially
behind schedule. I'm still optimistic that we can wrap this up pretty
soon, though.

This is what's blocking us:

- PR26509: Crash in InnerLoopVectorizer::vectorizeLoop()
  I'm waiting to hear what Cong comes up with, otherwise we can revert
r255691 on the branch

- Shrink-wrapping vs TLS: Davide and Quentin are working on it

- PR26600: Loop vectorization creates an unsafe out-of-bounds load
  There's a patch out: http://reviews.llvm.org/D17332
  But no comments yet.. Hal?

- PR26564: Performance regression in AA
  Patch in review, but it makes me a little uneasy since it's big and
requires pulling in some refactoring patches too :-/

- ARM: fix VFP asm constraints: http://reviews.llvm.org/D17349
  It's not a regression, but I'll take it if it lands real soon.

- PR26500: shrink-wrapping vs PPC
  Patch in review: http://reviews.llvm.org/D17294
  Looks like it's moving along.

- PR26081: Assertion failed: (BitWidth == RHS.BitWidth && ...
  I believe Matthias is working on it?
  Will revert r252839 to unblock otherwise.

- PR26485: regression lowering TLS access in C on Darwin
  Is no one looking? :-(

If you're on one of these bugs or code reviews, etc., please try to
prioritize them if you can.

Also, please let me know if my list is missing something.

Cheers,
Hans
___
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] [Release-testers] [3.8 Release] RC3 has been tagged

[Daniel Sanders via lldb-dev]

clang+llvm-3.8.0-rc3-x86_64-linux-gnu-debian8.tar.xz (sha1sum: 
2dedc6136d7cfbac8348652c543887964d92393c)
Native: All ok
Cross compiling to MIPS: All ok

clang+llvm-3.8.0-rc3-mips-linux-gnu.tar.xz (sha1sum: 
f286149dbb2ea7e194c5c3719b6cded476f6e65f)
All ok (aside from non-regression failures in check-all).
There were two kinds of check-all failure:
* mips64 sanitizers. Not a regression since mip64 sanitizers didn't 
ship in 3.7.1
* atomic tests fail due to missing -latomic on link. Not a regression 
since _no_ libc++ tests ran in 3.7.1 (this was obscured by the -s on llvm-lit).
Failing Tests (76):
AddressSanitizer-mips64-linux :: 
TestCases/Posix/coverage-direct-activation.cc
AddressSanitizer-mips64-linux :: 
TestCases/Posix/coverage-direct-large.cc
AddressSanitizer-mips64-linux :: TestCases/Posix/coverage-direct.cc
AddressSanitizer-mips64-linux :: 
TestCases/Posix/coverage-fork-direct.cc
AddressSanitizer-mips64-linux :: TestCases/Posix/coverage.cc
DataFlowSanitizer :: custom.cc
DataFlowSanitizer :: propagate.c
LeakSanitizer-AddressSanitizer :: TestCases/swapcontext.cc
LeakSanitizer-AddressSanitizer :: TestCases/use_registers.cc
LeakSanitizer-Standalone :: TestCases/swapcontext.cc
LeakSanitizer-Standalone :: TestCases/use_registers.cc
MemorySanitizer :: Linux/process_vm_readv.cc
MemorySanitizer :: allocator_mapping.cc
MemorySanitizer :: dlerror.cc
MemorySanitizer :: dtls_test.c
MemorySanitizer :: memcmp_test.cc
MemorySanitizer :: msan_print_shadow3.cc
MemorySanitizer :: param_tls_limit.cc
MemorySanitizer :: unaligned_read_origin.cc
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.SmallPreAllocatedStackThread
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.UnalignedLoad
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.UnalignedStore16
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.UnalignedStore16_precise
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.UnalignedStore16_precise2
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.UnalignedStore32
MemorySanitizer-Unit :: 
Msan-mips64-Test/MemorySanitizer.gethostbyname_r_erange
MemorySanitizer-Unit :: Msan-mips64-Test/MemorySanitizer.ptrtoint
MemorySanitizer-Unit :: Msan-mips64-Test/MemorySanitizer.shmat
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.SmallPreAllocatedStackThread
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedLoad
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore16
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore16_precise
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore16_precise2
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.UnalignedStore32
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.gethostbyname_r_erange
MemorySanitizer-Unit :: 
Msan-mips64-with-call-Test/MemorySanitizer.ptrtoint
SanitizerCommon-Unit :: 
Sanitizer-mips64-Test/SanitizerCommon.FileOps
SanitizerCommon-Unit :: 
Sanitizer-mips64-Test/SanitizerIoctl.KVM_GET_LAPIC
SanitizerCommon-Unit :: 
Sanitizer-mips64-Test/SanitizerIoctl.KVM_GET_MP_STATE
SanitizerCommon-asan :: Linux/getpwnam_r_invalid_user.cc
SanitizerCommon-lsan :: Linux/getpwnam_r_invalid_user.cc
ThreadSanitizer-mips64 :: atexit2.cc
ThreadSanitizer-mips64 :: deadlock_detector_stress_test.cc
ThreadSanitizer-mips64 :: java_alloc.cc
ThreadSanitizer-mips64 :: java_race_pc.cc
ThreadSanitizer-mips64 :: longjmp.cc
ThreadSanitizer-mips64 :: longjmp2.cc
ThreadSanitizer-mips64 :: longjmp3.cc
ThreadSanitizer-mips64 :: longjmp4.cc
ThreadSanitizer-mips64 :: map32bit.cc
ThreadSanitizer-mips64 :: race_on_mutex.c
ThreadSanitizer-mips64 :: signal_longjmp.cc
libc++ :: std/atomics/atomics.types.generic/integral.pass.cpp
libc++ :: 
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_strong.pass.cpp
libc++ :: 
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_strong_explicit.pass.cpp
libc++ :: 
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchange_weak.pass.cpp
libc++ :: 
std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_compare_exchan

Re: [lldb-dev] [Release-testers] [3.8 Release] RC3 has been tagged

[Daniel Sanders via lldb-dev]

> > clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> > My machine died during the check-all stage and disappeared from the
> network. I've fixed it and am currently running the last few bits of test-
> release.sh manually.
> 
> Thanks, let me know how this turns out.
> 
> So far, it sounds like there are no new issues in rc3, so I'm hoping
> we can make that the final version for 3.8.0 real soon.
> 
> Cheers,
> Hans
> 

'check-all' is still killing the machine but I think I know what the problem 
is. While investigating some of the rc2 problems I noticed that g++-multilib 
wasn't installed and this was disabling the mips64el sanitizers. Installing 
this didn't cause problems at the time but I've noticed that some of the 
mips64el sanitizer tests are very memory hungry. I noticed several occasions 
where parallel asan tests were consuming ~200% of RAM and it would have been 
swapping heavily (on a USB2 disk) to cope. If later tests require even more RAM 
then it would explain why the system stops responding. I'm going to uninstall 
g++-multilib and rebuild rc3. Hopefully that will make check-all work again.

For now, I've commented out the check-all command and uploaded 
clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz (sha1sum: 
e280bf6db094a81f22f4cdf6c0b5955493a11b05). I'm going to run this through my 
usual test-suites and I should have the results by this evening.


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

Re: [lldb-dev] [Release-testers] [3.8 Release] RC3 has been tagged

[Daniel Sanders via lldb-dev]

> > > clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> > > My machine died during the check-all stage and disappeared from 
> > > the
> > network. I've fixed it and am currently running the last few bits of test-
> > release.sh manually.
> >
> > Thanks, let me know how this turns out.
> >
> > So far, it sounds like there are no new issues in rc3, so I'm hoping
> > we can make that the final version for 3.8.0 real soon.
> >
> > Cheers,
> > Hans
> >
> 
> 'check-all' is still killing the machine but I think I know what the problem 
> is. While investigating some of the rc2 
> problems I noticed that g++-multilib wasn't installed and this was disabling 
> the mips64el sanitizers. Installing this 
> didn't cause problems at the time but I've noticed that some of the mips64el 
> sanitizer tests are very memory hungry. 
> I noticed several occasions where parallel asan tests were consuming ~200% of 
> RAM and it would have been 
> swapping heavily (on a USB2 disk) to cope. If later tests require even more 
> RAM then it would explain why the 
> system stops responding. I'm going to uninstall g++-multilib and rebuild rc3. 
> Hopefully that will make check-all work 
> again.

It seems there's was still just enough multilib support on the machine to 
trigger mips64el sanitizers again but having worked around that the parts of 
lit that aren't mips64el sanitizers are working so far. llvm-lit is still going 
but big-endian mips and cross compilation was fine so I'm expecting little 
endian to be ok too. It's showing an ETA of about 90 mins for the remaining 
tests from clang and llvm at the moment. I'm going to run the MIPS32 sanitizer 
lit tests after that.

Overall, I think we're probably ready for final. I just can't confirm that rc3 
was definitely ok for little endian mips yet.

> For now, I've commented out the check-all command and uploaded 
> clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz 
> (sha1sum: e280bf6db094a81f22f4cdf6c0b5955493a11b05). I'm going to run this 
> through my usual test-suites and I
> should have the results by this evening.

The LNT test-suite runs were ok with the rc3 build.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [3.8 Release] RC3 has been tagged

[Daniel Sanders via lldb-dev]

> > > > clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> > > > My machine died during the check-all stage and disappeared from 
> > > > the
> > > network. I've fixed it and am currently running the last few bits of test-
> > > release.sh manually.
> > >
> > > Thanks, let me know how this turns out.
> > >
> > > So far, it sounds like there are no new issues in rc3, so I'm hoping
> > > we can make that the final version for 3.8.0 real soon.
> > >
> > > Cheers,
> > > Hans
> > >
> >
> > 'check-all' is still killing the machine but I think I know what the 
> > problem is. While investigating some of the rc2
> > problems I noticed that g++-multilib wasn't installed and this was 
> > disabling the mips64el sanitizers. Installing this
> > didn't cause problems at the time but I've noticed that some of the 
> > mips64el sanitizer tests are very memory hungry.
> > I noticed several occasions where parallel asan tests were consuming ~200% 
> > of RAM and it would have been
> > swapping heavily (on a USB2 disk) to cope. If later tests require even more 
> > RAM then it would explain why the
> > system stops responding. I'm going to uninstall g++-multilib and rebuild 
> > rc3. Hopefully that will make check-all work
> > again.
> 
> It seems there's was still just enough multilib support on the machine to 
> trigger mips64el sanitizers again but having worked
> around that the parts of lit that aren't mips64el sanitizers are working so 
> far. llvm-lit is still going but big-endian mips and cross
> compilation was fine so I'm expecting little endian to be ok too. It's 
> showing an ETA of about 90 mins for the remaining tests
> from clang and llvm at the moment. I'm going to run the MIPS32 sanitizer lit 
> tests after that.

This is proving to be a long 90 mins :-). It's currently at 93% and estimating 
15 mins but that estimate has been slowly creeping upwards for the last hour or 
so. I'll check on it first thing in the morning.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [3.8 Release] RC3 has been tagged

[Daniel Sanders via lldb-dev]

> -Original Message-
> From: Daniel Sanders
> Sent: 02 March 2016 21:01
> To: Hans Wennborg
> Cc: release-test...@lists.llvm.org; llvm-dev; cfe-dev; openmp-dev (openmp-
> d...@lists.llvm.org); LLDB Dev
> Subject: RE: [Release-testers] [3.8 Release] RC3 has been tagged
> 
> > > > clang+llvm-3.8.0-rc3-mipsel-linux-gnu.tar.xz
> > > > My machine died during the check-all stage and disappeared from
> the
> > > network. I've fixed it and am currently running the last few bits of test-
> > > release.sh manually.
> > >
> > > Thanks, let me know how this turns out.
> > >
> > > So far, it sounds like there are no new issues in rc3, so I'm hoping
> > > we can make that the final version for 3.8.0 real soon.
> > >
> > > Cheers,
> > > Hans
> > >
> >
> > 'check-all' is still killing the machine but I think I know what the 
> > problem is.
> While investigating some of the rc2
> > problems I noticed that g++-multilib wasn't installed and this was disabling
> the mips64el sanitizers. Installing this
> > didn't cause problems at the time but I've noticed that some of the
> mips64el sanitizer tests are very memory hungry.
> > I noticed several occasions where parallel asan tests were consuming
> ~200% of RAM and it would have been
> > swapping heavily (on a USB2 disk) to cope. If later tests require even more
> RAM then it would explain why the
> > system stops responding. I'm going to uninstall g++-multilib and rebuild 
> > rc3.
> Hopefully that will make check-all work
> > again.
> 
> It seems there's was still just enough multilib support on the machine to
> trigger mips64el sanitizers again but having worked around that the parts of
> lit that aren't mips64el sanitizers are working so far. llvm-lit is still 
> going but
> big-endian mips and cross compilation was fine so I'm expecting little endian
> to be ok too. It's showing an ETA of about 90 mins for the remaining tests
> from clang and llvm at the moment. I'm going to run the MIPS32 sanitizer lit
> tests after that.
> 
> Overall, I think we're probably ready for final. I just can't confirm that 
> rc3 was
> definitely ok for little endian mips yet.

This has all finished now. All ok. There was one failure in rc3 that wasn't in 
rc2 (libc++ :: 
std/thread/thread.mutex/thread.lock/thread.lock.shared/thread.lock.shared.locking/lock.pass.cpp)
 but it's not a regression compared to 3.7.0 and a small increase in the time 
limit makes it pass.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [3.8 Release] 'final' has been tagged

[Daniel Sanders via lldb-dev]

Uploaded the following:
3d6cb2afdf6d984a087a60188bb41bbe3a8261bb  
clang+llvm-3.8.0-mipsel-linux-gnu.tar.xz
b4b3ef9231e8a686901f4078f3fe5534900f2a54  clang+llvm-3.8.0-mips-linux-gnu.tar.xz
95fd207d3aa3be42b27aa93d9c5c00f18508800f  
clang+llvm-3.8.0-x86_64-linux-gnu-debian8.tar.xz

The cross-compilation tests from x86_64 to mips are still running but all other 
tests have been re-run without regressions. In particular, the problems I had 
with the mipsel testing during rc3 have been resolved now that multilib support 
has been removed from that machine again.

From: Release-testers [release-testers-boun...@lists.llvm.org] on behalf of 
Hans Wennborg via Release-testers [release-test...@lists.llvm.org]
Sent: 03 March 2016 00:33
To: Release-testers
Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev
Subject: [Release-testers] [3.8 Release] 'final' has been tagged

Dear testers,

My list of blockers is empty, and there were no new problems
discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1].

Please build the final binaries and upload to the sftp.

For others following along: yes, this means 3.8.0 is complete, but it
takes a couple of days to get the source and binary tarballs built. I
will send the release announcement when everything's ready.

Many thanks for all your work!
Hans

 [1]. http://lists.llvm.org/pipermail/llvm-branch-commits/2016-March/009883.html
___
Release-testers mailing list
release-test...@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [Release-testers] [3.8 Release] 'final' has been tagged

[Daniel Sanders via lldb-dev]

> -Original Message-
> From: Daniel Sanders
> Sent: 06 March 2016 16:57
> To: Hans Wennborg; Release-testers
> Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev
> Subject: RE: [Release-testers] [3.8 Release] 'final' has been tagged
> 
> Uploaded the following:
> 3d6cb2afdf6d984a087a60188bb41bbe3a8261bb  clang+llvm-3.8.0-mipsel-
> linux-gnu.tar.xz
> b4b3ef9231e8a686901f4078f3fe5534900f2a54  clang+llvm-3.8.0-mips-linux-
> gnu.tar.xz
> 95fd207d3aa3be42b27aa93d9c5c00f18508800f  clang+llvm-3.8.0-x86_64-linux-
> gnu-debian8.tar.xz
> 
> The cross-compilation tests from x86_64 to mips are still running but all 
> other
> tests have been re-run without regressions. In particular, the problems I had
> with the mipsel testing during rc3 have been resolved now that multilib
> support has been removed from that machine again.

The cross compilation tests have just finished with no regressions. 
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [Attn: Bot Owners!] Raising CMake minimum version to 3.4.3

[Daniel Sanders via lldb-dev]

All the MIPS buildbots are ready too.

From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of NAKAMURA 
Takumi via llvm-dev
Sent: 25 May 2016 23:03
To: Chris Bieneman; llvm-...@lists.llvm.org; cfe-...@lists.llvm.org; 
lldb-dev@lists.llvm.org
Subject: Re: [llvm-dev] [Attn: Bot Owners!] Raising CMake minimum version to 
3.4.3

I am ready, regarding to, http://bb.pgr.jp/
On Wed, May 25, 2016 at 5:54 AM Chris Bieneman 
mailto:be...@apple.com>> wrote:
Meant to send this yesterday, but I want to remind everyone that we’re going to 
be raising the CMake minimum version to 3.4.3 next week.

If you maintain bots please ensure that your bots are updated by end of day 
5/29 so that we can move on 5/30 (next Monday).

I have already heard from most bot owners either saying they had made the 
change, or scheduled to make it.

If you have any questions or concerns please let me know.

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

Re: [lldb-dev] Release_38 cherry-picks

[Daniel Sanders via lldb-dev]

Hi,

You should get approval from the release manager (Tom Stellard) first.

> -Original Message-
> From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Francis
> Ricci via lldb-dev
> Sent: 07 June 2016 00:23
> To: LLDB
> Subject: [lldb-dev] Release_38 cherry-picks
> 
> Hi all,
> 
> I'd like to merge a few more small bugfixes onto the 38 release
> branch. I'll plan to do it tomorrow (3/7) in the evening if I don't
> hear any objections. Thanks!
> 
> r259433 - Fix getCompiler in unit testing framework on compiler symlinks
> r267459 - Add missing qRegisterInfo option to gdbremote testcase
> r271899 - Don't remove PIE executables when using svr4 packets
> 
> Francis
> ___
> 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] [llvm-dev] [3.7 Release] RC3 has been tagged, let's wrap this up

[Daniel Sanders via lldb-dev]

clang+llvm-3.7.0-rc3-mips-linux-gnu.tar.xz
All ok.

clang+llvm-3.7.0-rc3-mipsel-linux-gnu.tar.xz
All ok.

clang+llvm-3.7.0-rc3-x86_64-linux-gnu-ubuntu-14.04.tar.xz (cross compiling for 
Mips)
Still running the last few test-suite runs but no unexpected problems 
so far.
I say 'unexpected' because I updated to a new GCC cross-compilation 
toolchain which no longer contains certain multilibs. The three runs that 
depend on these removed multilibs (mips32r1 and mips64r1 n32/n64) failed as 
expected.

> -Original Message-
> From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of Hans
> Wennborg via llvm-dev
> Sent: 21 August 2015 01:52
> To: llvm-dev; cfe-...@lists.llvm.org; lldb-dev@lists.llvm.org; openmp-
> d...@lists.llvm.org
> Cc: Ben Pope; Pavel Labath; Nikola Smiljanić
> Subject: [llvm-dev] [3.7 Release] RC3 has been tagged, let's wrap this up
> 
> Hello everyone,
> 
> 3.7-rc3 has just been tagged. Testers, please test, build binaries,
> upload to the sftp and report results to this thread.
> 
> Again, a lot of patches got merged between rc2 and rc3, but hopefully
> nothing that should upset things.
> 
> One thing that did change is that the release script now correctly
> symlinks clang-tools-extra into the build. If this causes problems on
> your platform, please just remove it.
> 
> This is a release candidate in the real sense: at this point I have
> zero release blockers on my radar. I will now only accept fixes for
> critical regressions, and if nothing comes up, rc3 will be promoted to
> 3.7.0-final.
> 
> Documentation and release note patches are still welcome all the way
> up until the final tag goes in.
> 
> Issues that were on my radar, but I don't consider blocking:
> 
> - Sanitizer test failures on various platforms, e.g. PR24222. We never
> ran these tests in previous releases, so it's not a regression. It
> would be great if the sanitizer folks could look into the test
> failures, but it's not blocking 3.7.
> 
> - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in
> __cxa_allocate_exception", Renato will exclude libc++ from his build
> for now.
> 
> - Lack of key functions in some Instruction classes causing build
> failures without -fno-rtti
> (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No
> patches have been forthcoming, so this will not get fixed for 3.7. At
> least we correctly report -fno-rtti in llvm-config built with CMake
> now.
> 
> - r244221: "[SPARC] Don't compare arch name as a string, use the enum
> instead", owner is unresponsive.
> 
> - "[lldb] r245020 - [MIPS]Handle floating point and aggregate return
> types in SysV-mips [32 bit] ABI", owner is unresponsive.
> 
> 
> Cheers,
> Hans
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [3.7 Release] RC4 has been tagged

[Daniel Sanders via lldb-dev]

> Please build and test. If no new issues arise, I plan to tag this as
> 'final' tomorrow or Friday so we can ship the release next week.

I'm afraid I can't build and test that quickly with the equipment I have at the 
moment. The little endian build is running on machine that was designed to be a 
router and currently takes almost 24 hours due to lack of FPU, local disk, and 
RAM. The test-suite for this build used to take 3 days for the same reason 
(mostly the lack of FPU causing _massive_ numbers of kernel interrupts for FPU 
emulation) but I'm using a CI20 now that gets through it in a few hours thanks 
to its FPU.

Can you tag it on Monday instead?

> -Original Message-
> From: llvm-dev [mailto:llvm-dev-boun...@lists.llvm.org] On Behalf Of Hans
> Wennborg via llvm-dev
> Sent: 27 August 2015 00:44
> To: llvm-dev; cfe-...@lists.llvm.org; lldb-dev@lists.llvm.org; openmp-
> d...@lists.llvm.org; Dimitry Andric; Nikola Smiljanić; Sylvestre Ledru; Renato
> Golin; Ben Pope; Sebastian Dreßler; Pavel Labath; Ed Maste
> Subject: [llvm-dev] [3.7 Release] RC4 has been tagged
> 
> Dear testers,
> 
> 3.7.0-rc4 has just been tagged. It is identical to rc3, plus:
> 
> - r245902: Revert r245355: change of clang-tools-extra symlink in the
> release script
> - r245947: Merge of r245927: Fix LLDB build on MIPS
> - r245948: Deprecate the DataLayout on the TargetMachine, and backport
> the 3.8 API
> - Changes to the ReleaseNotes.
> 
> Those changes should all be safe, and I expect this to be an extremely
> short cycle.
> 
> Please build and test. If no new issues arise, I plan to tag this as
> 'final' tomorrow or Friday so we can ship the release next week.
> 
> Thanks,
> Hans
> ___
> LLVM Developers mailing list
> llvm-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [llvm-dev] [3.7 Release] RC4 has been tagged

[Daniel Sanders via lldb-dev]

> -Original Message-
> From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf
> Of Hans Wennborg
> Sent: 27 August 2015 15:51
> To: Daniel Sanders
> Cc: cfe-...@lists.llvm.org; lldb-dev@lists.llvm.org; openmp-
> d...@lists.llvm.org; Dimitry Andric; Nikola Smiljanić; Sylvestre Ledru; Renato
> Golin; Ben Pope; Sebastian Dreßler; Pavel Labath; Ed Maste; llvm-
> d...@lists.llvm.org
> Subject: Re: [llvm-dev] [3.7 Release] RC4 has been tagged
> 
> On Thu, Aug 27, 2015 at 6:43 AM, Daniel Sanders
>  wrote:
> >> Please build and test. If no new issues arise, I plan to tag this as
> >> 'final' tomorrow or Friday so we can ship the release next week.
> >
> > I'm afraid I can't build and test that quickly with the equipment I have at 
> > the
> moment. The little endian build is running on machine that was designed to
> be a router and currently takes almost 24 hours due to lack of FPU, local 
> disk,
> and RAM. The test-suite for this build used to take 3 days for the same
> reason (mostly the lack of FPU causing _massive_ numbers of kernel
> interrupts for FPU emulation) but I'm using a CI20 now that gets through it in
> a few hours thanks to its FPU.
> >
> > Can you tag it on Monday instead?
> 
> Since RC3 built fine for you, there really shouldn't be anything in
> RC4 that would cause problems. Maybe you could start a build to make
> sure it seems OK, but we don't wait for all the bootstrapping and
> test-suite to finish?

Ok. I'll get what I can done by the time you tag it and let you know if 
anything does cause problems.
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] [cfe-dev] [3.7 Release] 3.7.0-final has been tagged

[Daniel Sanders via lldb-dev]

clang+llvm-3.7.0-mips-linux-gnu.tar.xz
All ok

clang+llvm-3.7.0-mipsel-linux-gnu.tar.xz
All ok

clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz (cross compiling to Mips)
22 of 23 test suite runs ok. The 23rd is still running and is ok so far.

From: cfe-dev [cfe-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg via 
cfe-dev [cfe-...@lists.llvm.org]
Sent: 28 August 2015 02:46
To: llvm-dev; cfe-...@lists.llvm.org; lldb-dev@lists.llvm.org; 
openmp-...@lists.llvm.org; Dimitry Andric; Nikola Smiljanić; Sylvestre Ledru; 
Renato Golin; Ben Pope; Sebastian Dreßler; Pavel Labath; Ed Maste
Subject: [cfe-dev] [3.7 Release] 3.7.0-final has been tagged

On Wed, Aug 26, 2015 at 4:43 PM, Hans Wennborg  wrote:
> 3.7.0-rc4 has just been tagged. It is identical to rc3, plus:
>
> - r245902: Revert r245355: change of clang-tools-extra symlink in the
> release script
> - r245947: Merge of r245927: Fix LLDB build on MIPS
> - r245948: Deprecate the DataLayout on the TargetMachine, and backport
> the 3.8 API
> - Changes to the ReleaseNotes.
>
> Those changes should all be safe, and I expect this to be an extremely
> short cycle.
>
> Please build and test. If no new issues arise, I plan to tag this as
> 'final' tomorrow or Friday so we can ship the release next week.

I have promoted RC4 to final; 3.7.0 has reached its final state.

Thanks for all your hard work so far. Please build and upload binaries
with "-final", and let's ship this next week!

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

Re: [lldb-dev] [cfe-dev] [3.7 Release] 3.7.0-final has been tagged

[Daniel Sanders via lldb-dev]

The last one has finished and it was ok too.

From: hwennb...@google.com [hwennb...@google.com] on behalf of Hans Wennborg 
[h...@chromium.org]
Sent: 01 September 2015 18:43
To: Daniel Sanders
Cc: llvm-dev; cfe-...@lists.llvm.org; lldb-dev@lists.llvm.org; 
openmp-...@lists.llvm.org; Dimitry Andric; Nikola Smiljanić; Sylvestre Ledru; 
Renato Golin; Ben Pope; Sebastian Dreßler; Pavel Labath; Ed Maste
Subject: Re: [cfe-dev] [3.7 Release] 3.7.0-final has been tagged

Thanks! Let me know how the last one goes.

On Tue, Sep 1, 2015 at 8:16 AM, Daniel Sanders
 wrote:
> clang+llvm-3.7.0-mips-linux-gnu.tar.xz
> All ok
>
> clang+llvm-3.7.0-mipsel-linux-gnu.tar.xz
> All ok
>
> clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz (cross compiling to 
> Mips)
> 22 of 23 test suite runs ok. The 23rd is still running and is ok so far.
> 
> From: cfe-dev [cfe-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg via 
> cfe-dev [cfe-...@lists.llvm.org]
> Sent: 28 August 2015 02:46
> To: llvm-dev; cfe-...@lists.llvm.org; lldb-dev@lists.llvm.org; 
> openmp-...@lists.llvm.org; Dimitry Andric; Nikola Smiljanić; Sylvestre Ledru; 
> Renato Golin; Ben Pope; Sebastian Dreßler; Pavel Labath; Ed Maste
> Subject: [cfe-dev] [3.7 Release] 3.7.0-final has been tagged
>
> On Wed, Aug 26, 2015 at 4:43 PM, Hans Wennborg  wrote:
>> 3.7.0-rc4 has just been tagged. It is identical to rc3, plus:
>>
>> - r245902: Revert r245355: change of clang-tools-extra symlink in the
>> release script
>> - r245947: Merge of r245927: Fix LLDB build on MIPS
>> - r245948: Deprecate the DataLayout on the TargetMachine, and backport
>> the 3.8 API
>> - Changes to the ReleaseNotes.
>>
>> Those changes should all be safe, and I expect this to be an extremely
>> short cycle.
>>
>> Please build and test. If no new issues arise, I plan to tag this as
>> 'final' tomorrow or Friday so we can ship the release next week.
>
> I have promoted RC4 to final; 3.7.0 has reached its final state.
>
> Thanks for all your hard work so far. Please build and upload binaries
> with "-final", and let's ship this next week!
>
> Thanks,
> Hans
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev