llvm dev - Jan 2017 - [4.0.0 Release] Relase Candidate 1 has been tagged

Dear testers,

4.0.0-rc1 was just tagged from the branch, with r292377.

There are still open merge requests and bugs, but I'd like to get the
testing started to see what issues come up.

Please build, test, and upload binaries to the sftp. Let me know how
it goes. I'll upload source, docs, and your binaries to the web site
once their ready.

Thanks,
Hans

I'd like to test this, but I also need to test the corresponding libclang
version at the same time. Which revision of cfe is 4.0.0-rc1?

On Wed, Jan 18, 2017 at 10:45 AM, Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear testers,
>
> 4.0.0-rc1 was just tagged from the branch, with r292377.
>
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170118/9601f503/attachment.html>

Hi Hans,

I can test it on macOS. Is there a doc to describe what to test? I remember you
pointed me to a script once…
Anyone else involved in the release process on macOS?

Thanks,

— 
Mehdi



> On Jan 18, 2017, at 7:45 AM, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Dear testers,
> 
> 4.0.0-rc1 was just tagged from the branch, with r292377.
> 
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
> 
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

I tried to compile cfe 4.0.0-rc1 using llvm 4.0.0-rc1 and got this:

[ 63%] Building CXX object
lib/Serialization/CMakeFiles/clangSerialization.dir/ASTReader.cpp.o
/home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp: In lambda
function:
/home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp:1282:63:
error: invalid use of incomplete type ‘class llvm::Error’
       if (llvm::zlib::uncompress(Blob, Uncompressed, Record[0]) !              
^
In file included from
/home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp:73:0:
/home/andy/local/include/llvm/Support/Compression.h:21:7: note: forward
declaration of ‘class llvm::Error’
 class Error;
       ^
/home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp:1283:11:
error: ‘StatusOK’ is not a member of ‘llvm::zlib’
           llvm::zlib::StatusOK) {
           ^
lib/Serialization/CMakeFiles/clangSerialization.dir/build.make:86: recipe
for target
'lib/Serialization/CMakeFiles/clangSerialization.dir/ASTReader.cpp.o'
failed


I added to AstReader.cpp:
#include "llvm/Support/Error.h"

But there's still the other error.

On Wed, Jan 18, 2017 at 10:45 AM, Hans Wennborg via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Dear testers,
>
> 4.0.0-rc1 was just tagged from the branch, with r292377.
>
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170118/e107e383/attachment.html>

The script lives in the llvm repo: utils/release/test-release.sh.
You'll probably want to invoke it as test-release.sh -release 4.0.0
-rc
1 -triple x86_64-apple-darwin

On Wed, Jan 18, 2017 at 10:26 AM, Mehdi Amini <mehdi.amini at apple.com>
wrote:
> Hi Hans,
>
> I can test it on macOS. Is there a doc to describe what to test? I remember
you pointed me to a script once…
> Anyone else involved in the release process on macOS?
>
> Thanks,
>
> —
> Mehdi
>
>
>
>
>> On Jan 18, 2017, at 7:45 AM, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
>>
>> Dear testers,
>>
>> 4.0.0-rc1 was just tagged from the branch, with r292377.
>>
>> There are still open merge requests and bugs, but I'd like to get
the
>> testing started to see what issues come up.
>>
>> Please build, test, and upload binaries to the sftp. Let me know how
>> it goes. I'll upload source, docs, and your binaries to the web
site
>> once their ready.
>>
>> Thanks,
>> Hans
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>

If you're using the svn repository you can just check out the
RELEASE_400/rc1 tag of the cfe module.

If you're using the git mirror, the last cfe commit on the release_40
branch before the tag is 3a631d565d.

Thanks,
Hans

On Wed, Jan 18, 2017 at 10:11 AM, Andrew Kelley <superjoe30 at gmail.com>
wrote:
> I'd like to test this, but I also need to test the corresponding
libclang
> version at the same time. Which revision of cfe is 4.0.0-rc1?
>
> On Wed, Jan 18, 2017 at 10:45 AM, Hans Wennborg via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>>
>> Dear testers,
>>
>> 4.0.0-rc1 was just tagged from the branch, with r292377.
>>
>> There are still open merge requests and bugs, but I'd like to get
the
>> testing started to see what issues come up.
>>
>> Please build, test, and upload binaries to the sftp. Let me know how
>> it goes. I'll upload source, docs, and your binaries to the web
site
>> once their ready.
>>
>> Thanks,
>> Hans
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>

Looks like LLVM and clang are out-of-sync.

Using the script as Hans said worked for me:  test-release.sh -release 4.0.0 -rc
1 -triple x86_64-apple-darwin
(Triple is likely gonna be different for you).

— 
Mehdi
> On Jan 18, 2017, at 12:28 PM, Andrew Kelley via cfe-dev <cfe-dev at
lists.llvm.org> wrote:
> 
> I tried to compile cfe 4.0.0-rc1 using llvm 4.0.0-rc1 and got this:
> 
> [ 63%] Building CXX object
lib/Serialization/CMakeFiles/clangSerialization.dir/ASTReader.cpp.o
> /home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp: In lambda
function:
> /home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp:1282:63:
error: invalid use of incomplete type ‘class llvm::Error’
>        if (llvm::zlib::uncompress(Blob, Uncompressed, Record[0]) !>     
^
> In file included from
/home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp:73:0:
> /home/andy/local/include/llvm/Support/Compression.h:21:7: note: forward
declaration of ‘class llvm::Error’
>  class Error;
>        ^
> /home/andy/Downloads/cfe/rc1/lib/Serialization/ASTReader.cpp:1283:11:
error: ‘StatusOK’ is not a member of ‘llvm::zlib’
>            llvm::zlib::StatusOK) {
>            ^
> lib/Serialization/CMakeFiles/clangSerialization.dir/build.make:86: recipe
for target
'lib/Serialization/CMakeFiles/clangSerialization.dir/ASTReader.cpp.o'
failed
> 
> 
> I added to AstReader.cpp:
> #include "llvm/Support/Error.h"
> 
> But there's still the other error.
> 
> On Wed, Jan 18, 2017 at 10:45 AM, Hans Wennborg via llvm-dev <llvm-dev
at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
> Dear testers,
> 
> 4.0.0-rc1 was just tagged from the branch, with r292377.
> 
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
> 
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
<http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev>
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170118/167cc6be/attachment.html>

> On Jan 18, 2017, at 7:45 AM, Hans Wennborg via cfe-dev <cfe-dev at
lists.llvm.org> wrote:
> 
> Dear testers,
> 
> 4.0.0-rc1 was just tagged from the branch, with r292377.
> 
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
> 
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
I built successfully, it the something specific you do for testing?
Am I expected to upload clang+llvm-4.0.0-rc1-x86_64-apple-darwin.tar.xz
somewhere? (I don’t what sftp you’re referring to above).

Pardon my ignorance, first time I participate in the release process :)

Thanks,

Mehdi

On Wed, Jan 18, 2017 at 4:43 PM, Mehdi Amini <mehdi.amini at apple.com>
wrote:
>
>> On Jan 18, 2017, at 7:45 AM, Hans Wennborg via cfe-dev <cfe-dev at
lists.llvm.org> wrote:
>>
>> Dear testers,
>>
>> 4.0.0-rc1 was just tagged from the branch, with r292377.
>>
>> There are still open merge requests and bugs, but I'd like to get
the
>> testing started to see what issues come up.
>>
>> Please build, test, and upload binaries to the sftp. Let me know how
>> it goes. I'll upload source, docs, and your binaries to the web
site
>> once their ready.
>
> I built successfully, it the something specific you do for testing?
The script tests that bootstrapping and running all the lit tests work.

Some testers run the test-suite (which I'm not really familiar with
myself) and if they have other code bases they care about.

But running test-release.sh is what I'm asking for really.
> Am I expected to upload clang+llvm-4.0.0-rc1-x86_64-apple-darwin.tar.xz
somewhere? (I don’t what sftp you’re referring to above).
Yes. I've asked Anton to give you access.
>
> Pardon my ignorance, first time I participate in the release process :)
No problem at all, and thanks very much for doing this.

Cheers,
Hans

On 18 Jan 2017, at 16:45, Hans Wennborg via Release-testers <release-testers
at lists.llvm.org> wrote:
> Dear testers,
> 
> 4.0.0-rc1 was just tagged from the branch, with r292377.
> 
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
Unfortunately no builds for FreeBSD yet, as the Phase1 clang segfaults when
building AsmParser.cpp:

[  1%] Building CXX object
lib/MC/MCParser/CMakeFiles/LLVMMCParser.dir/AsmParser.cpp.o
cd
/home/dim/llvm-4.0.0/rc1/Phase2/Release/llvmCore-4.0.0-rc1.obj/lib/MC/MCParser
&& /home/dim/llvm-4.0
.0/rc1/Phase1/Release/llvmCore-4.0.0-rc1.install/usr/local/bin/clang++  
-DGTEST_HAS_RTTI=0 -D__STDC_CO
NSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-I/home/dim/llvm-4.0.0/rc1/Phase2/Release/ll
vmCore-4.0.0-rc1.obj/lib/MC/MCParser
-I/home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser -I/home/dim/ll
vm-4.0.0/rc1/Phase2/Release/llvmCore-4.0.0-rc1.obj/include
-I/home/dim/llvm-4.0.0/rc1/llvm.src/include
-I/usr/local/include  -fPIC -fvisibility-inlines-hidden -Wall -W
-Wno-unused-parameter -Wwrite-strings
-Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
-Wcovered-switch-default -Wnon-virtua
l-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -Werror=date-time
-std=c++11 -ffunction-sections -
fdata-sections -O3 -DNDEBUG    -fno-exceptions -fno-rtti -o
CMakeFiles/LLVMMCParser.dir/AsmParser.cpp.o
 -c /home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp
/home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2043:25:
warning: variable 'CppHashLocL
ineNo' is uninitialized when used here [-Wuninitialized]
        LastQueryLine = CppHashLocLineNo;
                        ^~~~~~~~~~~~~~~~
/home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2036:32: note:
initialize the variable
'CppHashLocLineNo' to silence this warning
      unsigned CppHashLocLineNo;
                               ^
                                = 0
/home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2155:71:
warning: variable 'LineNo' is
uninitialized when used here [-Wuninitialized]
  SMDiagnostic NewDiag(*Diag.getSourceMgr(), Diag.getLoc(), Filename, LineNo,
                                                                      ^~~~~~
/home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2152:13: note:
initialize the variable
'LineNo' to silence this warning
  int LineNo             ^
             = 0
clang-4.0: error: unable to execute command: Segmentation fault (core dumped)
clang-4.0: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 4.0.0 (tags/RELEASE_400/rc1)
Target: i386-unknown-freebsd10.3
Thread model: posix
InstalledDir:
/home/dim/llvm-4.0.0/rc1/Phase1/Release/llvmCore-4.0.0-rc1.install/usr/local/bin
clang-4.0: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang-4.0: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-4.0: note: diagnostic msg: /home/dim/tmp/AsmParser-c3ca7e.cpp
clang-4.0: note: diagnostic msg: /home/dim/tmp/AsmParser-c3ca7e.sh
clang-4.0: note: diagnostic msg:

********************
gmake[2]: *** [lib/MC/MCParser/CMakeFiles/LLVMMCParser.dir/build.make:87:
lib/MC/MCParser/CMakeFiles/LLVMMCParser.dir/AsmParser.cpp.o] Error 254

I thought this might be because r292133 was not merged yet, but I was wrong
about that, it *is* merged.

So I will have to investigate why it crashes here.

-Dimitry

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: Message signed with OpenPGP using GPGMail
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170119/a707b176/attachment.sig>

On Thu, Jan 19, 2017 at 12:12 AM, Dimitry Andric <dimitry at andric.com>
wrote:
> On 18 Jan 2017, at 16:45, Hans Wennborg via Release-testers
<release-testers at lists.llvm.org> wrote:
>> Dear testers,
>>
>> 4.0.0-rc1 was just tagged from the branch, with r292377.
>>
>> There are still open merge requests and bugs, but I'd like to get
the
>> testing started to see what issues come up.
>
> Unfortunately no builds for FreeBSD yet, as the Phase1 clang segfaults when
building AsmParser.cpp:
>
> [  1%] Building CXX object
lib/MC/MCParser/CMakeFiles/LLVMMCParser.dir/AsmParser.cpp.o
> cd
/home/dim/llvm-4.0.0/rc1/Phase2/Release/llvmCore-4.0.0-rc1.obj/lib/MC/MCParser
&& /home/dim/llvm-4.0
> .0/rc1/Phase1/Release/llvmCore-4.0.0-rc1.install/usr/local/bin/clang++  
-DGTEST_HAS_RTTI=0 -D__STDC_CO
> NSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS
-I/home/dim/llvm-4.0.0/rc1/Phase2/Release/ll
> vmCore-4.0.0-rc1.obj/lib/MC/MCParser
-I/home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser -I/home/dim/ll
> vm-4.0.0/rc1/Phase2/Release/llvmCore-4.0.0-rc1.obj/include
-I/home/dim/llvm-4.0.0/rc1/llvm.src/include
> -I/usr/local/include  -fPIC -fvisibility-inlines-hidden -Wall -W
-Wno-unused-parameter -Wwrite-strings
> -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
-Wcovered-switch-default -Wnon-virtua
> l-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -Werror=date-time
-std=c++11 -ffunction-sections -
> fdata-sections -O3 -DNDEBUG    -fno-exceptions -fno-rtti -o
CMakeFiles/LLVMMCParser.dir/AsmParser.cpp.o
>  -c /home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp
> /home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2043:25:
warning: variable 'CppHashLocL
> ineNo' is uninitialized when used here [-Wuninitialized]
>         LastQueryLine = CppHashLocLineNo;
>                         ^~~~~~~~~~~~~~~~
> /home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2036:32:
note: initialize the variable
> 'CppHashLocLineNo' to silence this warning
>       unsigned CppHashLocLineNo;
>                                ^
>                                 = 0
> /home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2155:71:
warning: variable 'LineNo' is
> uninitialized when used here [-Wuninitialized]
>   SMDiagnostic NewDiag(*Diag.getSourceMgr(), Diag.getLoc(), Filename,
LineNo,
>                                                                      
^~~~~~
> /home/dim/llvm-4.0.0/rc1/llvm.src/lib/MC/MCParser/AsmParser.cpp:2152:13:
note: initialize the variable
> 'LineNo' to silence this warning
>   int LineNo >             ^
>              = 0
> clang-4.0: error: unable to execute command: Segmentation fault (core
dumped)
> clang-4.0: error: clang frontend command failed due to signal (use -v to
see invocation)
> clang version 4.0.0 (tags/RELEASE_400/rc1)
> Target: i386-unknown-freebsd10.3
> Thread model: posix
> InstalledDir:
/home/dim/llvm-4.0.0/rc1/Phase1/Release/llvmCore-4.0.0-rc1.install/usr/local/bin
> clang-4.0: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
> clang-4.0: note: diagnostic msg:
> ********************
>
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> clang-4.0: note: diagnostic msg: /home/dim/tmp/AsmParser-c3ca7e.cpp
> clang-4.0: note: diagnostic msg: /home/dim/tmp/AsmParser-c3ca7e.sh
> clang-4.0: note: diagnostic msg:
>
> ********************
> gmake[2]: *** [lib/MC/MCParser/CMakeFiles/LLVMMCParser.dir/build.make:87:
lib/MC/MCParser/CMakeFiles/LLVMMCParser.dir/AsmParser.cpp.o] Error 254
>
> I thought this might be because r292133 was not merged yet, but I was wrong
about that, it *is* merged.
>
> So I will have to investigate why it crashes here.
Is this PR31692 that you filed today?

Hi,

Looks good on AArch64:
c6cc242dc3551c8465ba054e87e4d51df824aa17
clang+llvm-4.0.0-rc1-aarch64-linux-gnu.tar.xz

Regards,
Diana

On 18 January 2017 at 17:45, Hans Wennborg via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> Dear testers,
>
> 4.0.0-rc1 was just tagged from the branch, with r292377.
>
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
>
> Thanks,
> Hans
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

On 19 January 2017 at 17:43, Diana Picus via Release-testers
<release-testers at lists.llvm.org> wrote:
> Looks good on AArch64:
> c6cc242dc3551c8465ba054e87e4d51df824aa17
> clang+llvm-4.0.0-rc1-aarch64-linux-gnu.tar.xz
All good on ARM's side, too:

38e34694bb2ddd5178f48c2bef0aef65cc17b378
clang+llvm-4.0.0-rc1-armv7a-linux-gnueabihf.tar.xz

cheers,
--renato

Just pushed Darwin:

d93fca2905fece5b5392a0025c2f5f09f044a17c 
clang+llvm-4.0.0-rc1-x86_64-apple-darwin.tar.xz

— 
Mehdi
> On Jan 18, 2017, at 7:45 AM, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Dear testers,
> 
> 4.0.0-rc1 was just tagged from the branch, with r292377.
> 
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
> 
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

On Wed, Jan 18, 2017 at 7:45 AM, Hans Wennborg via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Dear testers,
>
> 4.0.0-rc1 was just tagged from the branch, with r292377.
>
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
We have Clang/llvm for Yocto project/OpenEmbedded as well and 4.0.0
branch is working fine for the project as well.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
>
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

Hi,

FYI, I added a Green dragon job to build and test (stage 1 only right now) the
release branch:
http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA-release-4/
<http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA-release-4/>

— 
Mehdi
> On Jan 18, 2017, at 7:45 AM, Hans Wennborg via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> Dear testers,
> 
> 4.0.0-rc1 was just tagged from the branch, with r292377.
> 
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
> 
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
> 
> Thanks,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170120/3a6e6e16/attachment.html>

Very cool initiative! Thank you!

On Fri, Jan 20, 2017, at 10:59 AM, Mehdi Amini via cfe-dev
wrote:
> Hi,
> 
> FYI, I added a Green dragon job to build and test (stage 1 only right
> now) the release branch:
> http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA-release-4/
>
<http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA-release-4/>
> 
> — 
> Mehdi
> 
> > On Jan 18, 2017, at 7:45 AM, Hans Wennborg via llvm-dev <llvm-dev
at lists.llvm.org> wrote:
> > 
> > Dear testers,
> > 
> > 4.0.0-rc1 was just tagged from the branch, with r292377.
> > 
> > There are still open merge requests and bugs, but I'd like to get
the
> > testing started to see what issues come up.
> > 
> > Please build, test, and upload binaries to the sftp. Let me know how
> > it goes. I'll upload source, docs, and your binaries to the web
site
> > once their ready.
> > 
> > Thanks,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

Hi,
updated OpenMandriva packaging. Looks good, so far passes testing on all 4
supported arches (x86_32, x86_64, armv7hnl, aarch64) after fixing one build
issue in clang-tools-extra:

FAILED: lib64/libclangIncludeFixerPlugin.so.4.0.0
: && /usr/bin/clang++  -fPIC -Os  -pipe -Wformat -Werror=format-security
-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4  -fPIC
-fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter
-Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic
-Wno-long-long -Wcovered-switch-default -Wnon-virtual-dt
or -Wdelete-non-virtual-dtor -Wstring-conversion -Werror=date-time
-std=c++1y -fcolor-diagnostics -ffunction-sections -fdata-sections
-fno-common -Woverloaded-virtual -Wno-nested-anon-types -Os  -pipe -Wformat
-Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector
--param=ssp-buffer-size=4  -fPIC  -L/home/bero/abf/llvm/BUIL
D/llvm-4.0.0.src/build/lib64 -Wl,-z,defs   -Wl,-O3 -Wl,--gc-sections
-shared -Wl,-soname,libclangIncludeFixerPlugin.so.4.0 -o
lib64/libclangIncludeFixerPlugin.so.4.0.0
tools/clang/tools/extra/include-fixer/plugin/CMakeFiles/clangIncludeFixerPlugin.dir/IncludeFixerPlugin.cpp.o
 lib64/libclangAST.so.4.0.0 lib64/libclangBasic.so.4.0.
0 lib64/libclangFrontend.so.4.0.0 lib64/libclangIncludeFixer.so.4.0.0
lib64/libclangParse.so.4.0.0 lib64/libclangSema.so.4.0.0
lib64/libclangTooling.so.4.0.0 lib64/libLLVMSupport.so.4.0.0 && :
tools/clang/tools/extra/include-fixer/plugin/CMakeFiles/clangIncludeFixerPlugin.dir/IncludeFixerPlugin.cpp.o:/home/bero/abf/llvm/BUILD/llvm-4.0.0.src/tools/clang/tools/extra/include-fixer/plugin/IncludeFixerPlugin.cpp:function
std::thread::thread<std::__future_base::_Async_state_impl<std::_Bind_simple<std::function<std::unique_ptr
<clang::include_fixer::SymbolIndex,
std::default_delete<clang::include_fixer::SymbolIndex> > ()> ()>,
std::unique_ptr<clang::include_fixer::SymbolIndex,
std::default_delete<clang::include_fixer::SymbolIndex>
>
>::_Async_state_impl(std::_Bind_simple<std::function<std::unique_ptr<clang::include_fixer::SymbolIndex,
std::default_delet
e<clang::include_fixer::SymbolIndex> > ()>
()>&&)::{lambda()#1}>(std::__future_base::_Async_state_impl<std::_Bind_simple<std::function<std::unique_ptr<clang::include_fixer::SymbolIndex,
std::default_delete<clang::include_fixer::SymbolIndex> > ()> ()>,
std::unique_ptr<clang::include_fixer::SymbolIndex,
std::default_delete<clang::in
clude_fixer::SymbolIndex> >
>::_Async_state_impl(std::_Bind_simple<std::function<std::unique_ptr<clang::include_fixer::SymbolIndex,
std::default_delete<clang::include_fixer::SymbolIndex> > ()>
()>&&)::{lambda()#1}&&): error: undefined reference to
'pthread_create'
clang-4.0: error: linker command failed with exit code 1 (use -v to see
invocation)
ninja: build stopped: subcommand failed.

Patch for this issue is attached (but will likely break Windows builds -
probably needs a platform check added).

ttyl
bero

On 18 January 2017 at 16:45, Hans Wennborg via Release-testers <
release-testers at lists.llvm.org> wrote:
> Dear testers,
>
> 4.0.0-rc1 was just tagged from the branch, with r292377.
>
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
>
> Thanks,
> Hans
> _______________________________________________
> Release-testers mailing list
> Release-testers at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170120/9e180d36/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: llvm-4.0.0-rc1-include-fixer-compile.patch
Type: text/x-patch
Size: 351 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20170120/9e180d36/attachment.bin>

Le 18/01/2017 à 16:45, Hans Wennborg via Release-testers a écrit
:
> Dear testers,
>
> 4.0.0-rc1 was just tagged from the branch, with r292377.
>
> There are still open merge requests and bugs, but I'd like to get the
> testing started to see what issues come up.
>
> Please build, test, and upload binaries to the sftp. Let me know how
> it goes. I'll upload source, docs, and your binaries to the web site
> once their ready.
All green on all Debian official archs:
https://buildd.debian.org/status/package.php?p=llvm-toolchain-4.0
(amd64, arm64, armel, armhf, i386, mips, mips64el, mipsel, ppc64el,
s390x + powerpc & sparc64).

S

On Fri, Jan 20, 2017 at 2:35 PM, Bernhard Rosenkränzer
<bernhard.rosenkranzer at linaro.org> wrote:
> Hi,
> updated OpenMandriva packaging. Looks good, so far passes testing on all 4
> supported arches (x86_32, x86_64, armv7hnl, aarch64) after fixing one build
> issue in clang-tools-extra:
>
> FAILED: lib64/libclangIncludeFixerPlugin.so.4.0.0
> : && /usr/bin/clang++  -fPIC -Os  -pipe -Wformat
-Werror=format-security
> -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4  -fPIC
-fPIC
> -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings
> -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long
> -Wcovered-switch-default -Wnon-virtual-dt
> or -Wdelete-non-virtual-dtor -Wstring-conversion -Werror=date-time
> -std=c++1y -fcolor-diagnostics -ffunction-sections -fdata-sections
> -fno-common -Woverloaded-virtual -Wno-nested-anon-types -Os  -pipe -Wformat
> -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector
> --param=ssp-buffer-size=4  -fPIC  -L/home/bero/abf/llvm/BUIL
> D/llvm-4.0.0.src/build/lib64 -Wl,-z,defs   -Wl,-O3 -Wl,--gc-sections
-shared
> -Wl,-soname,libclangIncludeFixerPlugin.so.4.0 -o
> lib64/libclangIncludeFixerPlugin.so.4.0.0
>
tools/clang/tools/extra/include-fixer/plugin/CMakeFiles/clangIncludeFixerPlugin.dir/IncludeFixerPlugin.cpp.o
> lib64/libclangAST.so.4.0.0 lib64/libclangBasic.so.4.0.
> 0 lib64/libclangFrontend.so.4.0.0 lib64/libclangIncludeFixer.so.4.0.0
> lib64/libclangParse.so.4.0.0 lib64/libclangSema.so.4.0.0
> lib64/libclangTooling.so.4.0.0 lib64/libLLVMSupport.so.4.0.0 && :
>
tools/clang/tools/extra/include-fixer/plugin/CMakeFiles/clangIncludeFixerPlugin.dir/IncludeFixerPlugin.cpp.o:/home/bero/abf/llvm/BUILD/llvm-4.0.0.src/tools/clang/tools/extra/include-fixer/plugin/IncludeFixerPlugin.cpp:function
>
std::thread::thread<std::__future_base::_Async_state_impl<std::_Bind_simple<std::function<std::unique_ptr
> <clang::include_fixer::SymbolIndex,
> std::default_delete<clang::include_fixer::SymbolIndex> > ()>
()>,
> std::unique_ptr<clang::include_fixer::SymbolIndex,
> std::default_delete<clang::include_fixer::SymbolIndex> >
>>::_Async_state_impl(std::_Bind_simple<std::function<std::unique_ptr<clang::include_fixer::SymbolIndex,
> std::default_delet
> e<clang::include_fixer::SymbolIndex> > ()>
>
()>&&)::{lambda()#1}>(std::__future_base::_Async_state_impl<std::_Bind_simple<std::function<std::unique_ptr<clang::include_fixer::SymbolIndex,
> std::default_delete<clang::include_fixer::SymbolIndex> > ()>
()>,
> std::unique_ptr<clang::include_fixer::SymbolIndex,
> std::default_delete<clang::in
> clude_fixer::SymbolIndex> >
>>::_Async_state_impl(std::_Bind_simple<std::function<std::unique_ptr<clang::include_fixer::SymbolIndex,
> std::default_delete<clang::include_fixer::SymbolIndex> > ()>
> ()>&&)::{lambda()#1}&&): error: undefined reference to
'pthread_create'
> clang-4.0: error: linker command failed with exit code 1 (use -v to see
> invocation)
> ninja: build stopped: subcommand failed.
>
> Patch for this issue is attached (but will likely break Windows builds -
> probably needs a platform check added).
Benjamin landed that fix in r291892 which was just merged, so
hopefully that's all good now.

Thanks,
Hans

> On 18 January 2017 at 16:45, Hans Wennborg via Release-testers
> <release-testers at lists.llvm.org> wrote:
>>
>> Dear testers,
>>
>> 4.0.0-rc1 was just tagged from the branch, with r292377.
>>
>> There are still open merge requests and bugs, but I'd like to get
the
>> testing started to see what issues come up.
>>
>> Please build, test, and upload binaries to the sftp. Let me know how
>> it goes. I'll upload source, docs, and your binaries to the web
site
>> once their ready.
>>
>> Thanks,
>> Hans
>> _______________________________________________
>> Release-testers mailing list
>> Release-testers at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers
>
>