Hi all, The 3.7 release branch was created from trunk at r242221 today (around 10:40 pm UTC). Branch policy: - Any doc changes can go in. Updates to the release notes are highly encouraged, and should be committed directly to the branch. - All other patches should be approved by the release manager (me) and the appropriate code owner. To get a change merged, commit it to trunk, and then reply to the commit email with myself and the code owner cc'd, asking for approval. - Fixes to complete existing features may be merged. However, the features must be completed before Phase II of testing starts, otherwise they should be disabled. If you recently committed something experimental to trunk, please make sure it's disabled on the branch. - For any bug fixes that you think might apply to the release branch, please cc me on the commit message. Cheers, Hans
On Tue, Jul 14, 2015 at 5:25 PM, Hans Wennborg <hans at chromium.org> wrote:> Hi all, > > The 3.7 release branch was created from trunk at r242221 today (around > 10:40 pm UTC). > > Branch policy: > > - Any doc changes can go in. Updates to the release notes are highly > encouraged, and should be committed directly to the branch. > > - All other patches should be approved by the release manager (me) and > the appropriate code owner. To get a change merged, commit it to > trunk, and then reply to the commit email with myself and the code > owner cc'd, asking for approval. > > - Fixes to complete existing features may be merged. However, the > features must be completed before Phase II of testing starts, > otherwise they should be disabled. If you recently committed something > experimental to trunk, please make sure it's disabled on the branch. > > - For any bug fixes that you think might apply to the release branch, > please cc me on the commit message. >Do we have any official documentation of these bullet points? It might be worth updating http://llvm.org/docs/HowToReleaseLLVM.html with some information to limit the amount of "tribal knowledge" involved in our release process (which has bitten us in the past). -- Sean Silva> > Cheers, > Hans > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150714/bddff8c6/attachment.html>
I'm getting these errors: C:\llvm-svn>svn up -r242221 Updating '.': svn: E730054: Unable to connect to a repository at URL ' http://llvm.org/svn/llvm-project/llvm/trunk' svn: E730054: Error running context: An existing connection was forcibly closed by the remote host. C:\llvm-svn>svn up -r242221 Updating '.': svn: E175012: Unable to connect to a repository at URL ' http://llvm.org/svn/llvm-project/llvm/trunk' svn: E175012: Connection timed out Is it the case that the server is down at the moment, or overloaded with a lot of people trying to download 3.7? If so, fair enough, I'll try again later; just wanting to make sure it's not the case that I've got the wrong address or have forgotten something important about how to use svn or something like that. On Wed, Jul 15, 2015 at 1:25 AM, Hans Wennborg <hans at chromium.org> wrote:> Hi all, > > The 3.7 release branch was created from trunk at r242221 today (around > 10:40 pm UTC). > > Branch policy: > > - Any doc changes can go in. Updates to the release notes are highly > encouraged, and should be committed directly to the branch. > > - All other patches should be approved by the release manager (me) and > the appropriate code owner. To get a change merged, commit it to > trunk, and then reply to the commit email with myself and the code > owner cc'd, asking for approval. > > - Fixes to complete existing features may be merged. However, the > features must be completed before Phase II of testing starts, > otherwise they should be disabled. If you recently committed something > experimental to trunk, please make sure it's disabled on the branch. > > - For any bug fixes that you think might apply to the release branch, > please cc me on the commit message. > > Cheers, > Hans > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150715/98315c9e/attachment.html>
Hi Russell,
I tried to check out with command "svn co
http://llvm.org/svn/llvm-project/llvm/trunk" , it works. It seems the SVN
server is not down.
-- Kun Ling
------------------ Original ------------------
From: "Russell Wallace"<russell.wallace at gmail.com>;
Date: Tue, Jul 14, 2015 07:30 PM
To: "Hans Wennborg"<hans at chromium.org>;
Cc: "lldb-dev"<lldb-dev at cs.uiuc.edu>;
"cfe-dev"<cfe-dev at cs.uiuc.edu>;
"llvmdev"<llvmdev at cs.uiuc.edu>;
Subject: Re: [cfe-dev] [LLVMdev] [3.7 Release] We have branched
I'm getting these errors:
C:\llvm-svn>svn up -r242221
Updating '.':
svn: E730054: Unable to connect to a repository at URL
'http://llvm.org/svn/llvm-project/llvm/trunk'
svn: E730054: Error running context: An existing connection was forcibly closed
by the remote host.
C:\llvm-svn>svn up -r242221
Updating '.':
svn: E175012: Unable to connect to a repository at URL
'http://llvm.org/svn/llvm-project/llvm/trunk'
svn: E175012: Connection timed out
Is it the case that the server is down at the moment, or overloaded with a lot
of people trying to download 3.7? If so, fair enough, I'll try again later;
just wanting to make sure it's not the case that I've got the wrong
address or have forgotten something important about how to use svn or something
like that.
On Wed, Jul 15, 2015 at 1:25 AM, Hans Wennborg <hans at chromium.org>
wrote:
Hi all,
The 3.7 release branch was created from trunk at r242221 today (around
10:40 pm UTC).
Branch policy:
- Any doc changes can go in. Updates to the release notes are highly
encouraged, and should be committed directly to the branch.
- All other patches should be approved by the release manager (me) and
the appropriate code owner. To get a change merged, commit it to
trunk, and then reply to the commit email with myself and the code
owner cc'd, asking for approval.
- Fixes to complete existing features may be merged. However, the
features must be completed before Phase II of testing starts,
otherwise they should be disabled. If you recently committed something
experimental to trunk, please make sure it's disabled on the branch.
- For any bug fixes that you think might apply to the release branch,
please cc me on the commit message.
Cheers,
Hans
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150715/083bcc38/attachment.html>
Hi, I see there's no rc1 tag yet so I'll try the branch directly with D10715 (switch to cmake) and D6563 (enables directly testing branch with test-release.sh) applied.> -----Original Message----- > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] > On Behalf Of Hans Wennborg > Sent: 15 July 2015 01:25 > To: llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > Subject: [LLVMdev] [3.7 Release] We have branched > > Hi all, > > The 3.7 release branch was created from trunk at r242221 today (around > 10:40 pm UTC). > > Branch policy: > > - Any doc changes can go in. Updates to the release notes are highly > encouraged, and should be committed directly to the branch. > > - All other patches should be approved by the release manager (me) and > the appropriate code owner. To get a change merged, commit it to > trunk, and then reply to the commit email with myself and the code > owner cc'd, asking for approval. > > - Fixes to complete existing features may be merged. However, the > features must be completed before Phase II of testing starts, > otherwise they should be disabled. If you recently committed something > experimental to trunk, please make sure it's disabled on the branch. > > - For any bug fixes that you think might apply to the release branch, > please cc me on the commit message. > > Cheers, > Hans > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Basic test results on Windows 7, visual studio 2013 (64 bit):
Build clang with visual studio - okay
Build clang with itself - okay
Build Python - okay
Build Ruby - fails on conftest.c, but 3.6 also failed so this is not a
regression bug
Build Perl - fails. 3.6 also failed, but I think the error message was
different, so this could be a regression bug but hopefully it's actually an
improvement. Current error message:
cl -c -I. -nologo -GF -W3 -I..\lib\CORE -I.\include -I. -I..
-DWIN32 -D_CONSOLE -DNO_STRICT -DWIN64 -DCONSERVATIVE
-D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -DPERLDLL -DPERL_CORE
-O1 -MD -Zi -DNDEBUG -GL -fp:precise -DPERL_TEXTMODE_SCRIPTS
-DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj
perllib.c
clang-cl.exe: warning: argument unused during compilation: '-GL'
In file included from perllib.c:10:
In file included from ..\lib\CORE\perl.h:3060:
In file included from .\win32thread.h:4:
./win32.h(284,25) : error: 'selectany' can only be applied to data
items
with external linkage
On Wed, Jul 15, 2015 at 1:25 AM, Hans Wennborg <hans at chromium.org>
wrote:
> Hi all,
>
> The 3.7 release branch was created from trunk at r242221 today (around
> 10:40 pm UTC).
>
> Branch policy:
>
> - Any doc changes can go in. Updates to the release notes are highly
> encouraged, and should be committed directly to the branch.
>
> - All other patches should be approved by the release manager (me) and
> the appropriate code owner. To get a change merged, commit it to
> trunk, and then reply to the commit email with myself and the code
> owner cc'd, asking for approval.
>
> - Fixes to complete existing features may be merged. However, the
> features must be completed before Phase II of testing starts,
> otherwise they should be disabled. If you recently committed something
> experimental to trunk, please make sure it's disabled on the branch.
>
> - For any bug fixes that you think might apply to the release branch,
> please cc me on the commit message.
>
> Cheers,
> Hans
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20150715/98bf790c/attachment.html>
On Tue, Jul 14, 2015 at 5:41 PM, Sean Silva <chisophugis at gmail.com> wrote:> > > On Tue, Jul 14, 2015 at 5:25 PM, Hans Wennborg <hans at chromium.org> wrote: >> >> Hi all, >> >> The 3.7 release branch was created from trunk at r242221 today (around >> 10:40 pm UTC). >> >> Branch policy: >> >> - Any doc changes can go in. Updates to the release notes are highly >> encouraged, and should be committed directly to the branch. >> >> - All other patches should be approved by the release manager (me) and >> the appropriate code owner. To get a change merged, commit it to >> trunk, and then reply to the commit email with myself and the code >> owner cc'd, asking for approval. >> >> - Fixes to complete existing features may be merged. However, the >> features must be completed before Phase II of testing starts, >> otherwise they should be disabled. If you recently committed something >> experimental to trunk, please make sure it's disabled on the branch. >> >> - For any bug fixes that you think might apply to the release branch, >> please cc me on the commit message. > > > Do we have any official documentation of these bullet points? It might be > worth updating http://llvm.org/docs/HowToReleaseLLVM.html with some > information to limit the amount of "tribal knowledge" involved in our > release process (which has bitten us in the past).I'm basing them (and the whole release thing, really) on how Bill used to do it and the emails he sent out. I think that corresponds pretty well to what's on the HowToReleaseLLVM page under the "Release Timeline" and "Release Patch Rules". Was there anything in my email you think is missing from there? Thanks, Hans
Test-release.sh is giving 'make check-all' failures I didn't used to
have but there all (except one) for projects we didn't build in 3.6.2 so
that's not a big problem.
The failures are:
AddressSanitizer-mips-linux :: TestCases/Linux/kernel-area.cc
AddressSanitizer-mips-linux :: TestCases/Posix/coverage-direct-large.cc
Clang :: Driver/cuda-options.cu
UBSan-ASan-mips :: TestCases/Float/cast-overflow.cpp
UBSan-Standalone-mips :: TestCases/Float/cast-overflow.cpp
libc++abi :: backtrace_test.pass.cpp
libc++abi :: test_demangle.pass.cpp
I had to kill an excessively long 'llc -march=r600 -mcpu=cypress'
process (>500 minutes) to make the tests finish. I assume it's one of
those failures.
Tom: Are you aware of any r600 tests that run forever?
Sagar: Could you look into the two ubsan failures?
Kumar: Could you look into the two asan failures?
The test system is running 32-bit Debian Jessie for mips (big-endian) and is a
MIPS64r2 CPU. You'll need to configure llvm with
-DLLVM_HOST_TRIPLE=mips-linux-gnu.
> -----Original Message-----
> From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at
cs.uiuc.edu]
> On Behalf Of Daniel Sanders
> Sent: 15 July 2015 11:26
> To: Hans Wennborg; llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu
> Subject: Re: [cfe-dev] [LLVMdev] [3.7 Release] We have branched
>
> Hi,
>
> I see there's no rc1 tag yet so I'll try the branch directly with
D10715 (switch to
> cmake) and D6563 (enables directly testing branch with test-release.sh)
> applied.
>
> > -----Original Message-----
> > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-
> bounces at cs.uiuc.edu]
> > On Behalf Of Hans Wennborg
> > Sent: 15 July 2015 01:25
> > To: llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu
> > Subject: [LLVMdev] [3.7 Release] We have branched
> >
> > Hi all,
> >
> > The 3.7 release branch was created from trunk at r242221 today (around
> > 10:40 pm UTC).
> >
> > Branch policy:
> >
> > - Any doc changes can go in. Updates to the release notes are highly
> > encouraged, and should be committed directly to the branch.
> >
> > - All other patches should be approved by the release manager (me) and
> > the appropriate code owner. To get a change merged, commit it to
> > trunk, and then reply to the commit email with myself and the code
> > owner cc'd, asking for approval.
> >
> > - Fixes to complete existing features may be merged. However, the
> > features must be completed before Phase II of testing starts,
> > otherwise they should be disabled. If you recently committed something
> > experimental to trunk, please make sure it's disabled on the
branch.
> >
> > - For any bug fixes that you think might apply to the release branch,
> > please cc me on the commit message.
> >
> > Cheers,
> > Hans
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
I should have added Mohit instead of Kumar. Sorry.> -----Original Message----- > From: Daniel Sanders > Sent: 16 July 2015 11:10 > To: Hans Wennborg; llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > Cc: Tom Stellard (tom at stellard.net); Sagar Thakur; Kumar Sukhani > Subject: RE: [LLVMdev] [3.7 Release] We have branched > > Test-release.sh is giving 'make check-all' failures I didn't used to have but > there all (except one) for projects we didn't build in 3.6.2 so that's not a big > problem. > > The failures are: > AddressSanitizer-mips-linux :: TestCases/Linux/kernel-area.cc > AddressSanitizer-mips-linux :: TestCases/Posix/coverage-direct-large.cc > Clang :: Driver/cuda-options.cu > UBSan-ASan-mips :: TestCases/Float/cast-overflow.cpp > UBSan-Standalone-mips :: TestCases/Float/cast-overflow.cpp > libc++abi :: backtrace_test.pass.cpp > libc++abi :: test_demangle.pass.cpp > I had to kill an excessively long 'llc -march=r600 -mcpu=cypress' process (>500 > minutes) to make the tests finish. I assume it's one of those failures. > > Tom: Are you aware of any r600 tests that run forever? > > Sagar: Could you look into the two ubsan failures? > Mohit: Could you look into the two asan failures? > The test system is running 32-bit Debian Jessie for mips (big-endian) and is a > MIPS64r2 CPU. You'll need to configure llvm with - > DLLVM_HOST_TRIPLE=mips-linux-gnu. > > > -----Original Message----- > > From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev- > bounces at cs.uiuc.edu] > > On Behalf Of Daniel Sanders > > Sent: 15 July 2015 11:26 > > To: Hans Wennborg; llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > > Subject: Re: [cfe-dev] [LLVMdev] [3.7 Release] We have branched > > > > Hi, > > > > I see there's no rc1 tag yet so I'll try the branch directly with D10715 (switch > to > > cmake) and D6563 (enables directly testing branch with test-release.sh) > > applied. > > > > > -----Original Message----- > > > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev- > > bounces at cs.uiuc.edu] > > > On Behalf Of Hans Wennborg > > > Sent: 15 July 2015 01:25 > > > To: llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > > > Subject: [LLVMdev] [3.7 Release] We have branched > > > > > > Hi all, > > > > > > The 3.7 release branch was created from trunk at r242221 today (around > > > 10:40 pm UTC). > > > > > > Branch policy: > > > > > > - Any doc changes can go in. Updates to the release notes are highly > > > encouraged, and should be committed directly to the branch. > > > > > > - All other patches should be approved by the release manager (me) and > > > the appropriate code owner. To get a change merged, commit it to > > > trunk, and then reply to the commit email with myself and the code > > > owner cc'd, asking for approval. > > > > > > - Fixes to complete existing features may be merged. However, the > > > features must be completed before Phase II of testing starts, > > > otherwise they should be disabled. If you recently committed something > > > experimental to trunk, please make sure it's disabled on the branch. > > > > > > - For any bug fixes that you think might apply to the release branch, > > > please cc me on the commit message. > > > > > > Cheers, > > > Hans > > > _______________________________________________ > > > LLVM Developers mailing list > > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > _______________________________________________ > > cfe-dev mailing list > > cfe-dev at cs.uiuc.edu > > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
Tom: I've identified the problem test as test/CodeGen/AMDGPU/infinite-loop-evergreen.ll. Please see https://llvm.org/bugs/show_bug.cgi?id=24147 for details. Sagar: The ticket for the ubsan failures is https://llvm.org/bugs/show_bug.cgi?id=24152. I've put them both on the same ticket since it's the same test file. Mohit: The tickets for the asan failures are https://llvm.org/bugs/show_bug.cgi?id=24150 and https://llvm.org/bugs/show_bug.cgi?id=24151. Nitesh: The tickets for the libc++abi failures are https://llvm.org/bugs/show_bug.cgi?id=24148 and https://llvm.org/bugs/show_bug.cgi?id=24149.> -----Original Message----- > From: Daniel Sanders > Sent: 16 July 2015 11:37 > To: 'Hans Wennborg'; 'llvmdev'; 'cfe-dev'; 'lldb-dev at cs.uiuc.edu' > Cc: Tom Stellard (tom at stellard.net); Sagar Thakur; Mohit Bhakkad > Subject: RE: [LLVMdev] [3.7 Release] We have branched > > I should have added Mohit instead of Kumar. Sorry. > > > -----Original Message----- > > From: Daniel Sanders > > Sent: 16 July 2015 11:10 > > To: Hans Wennborg; llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > > Cc: Tom Stellard (tom at stellard.net); Sagar Thakur; Kumar Sukhani > > Subject: RE: [LLVMdev] [3.7 Release] We have branched > > > > Test-release.sh is giving 'make check-all' failures I didn't used to have but > > there all (except one) for projects we didn't build in 3.6.2 so that's not a big > > problem. > > > > The failures are: > > AddressSanitizer-mips-linux :: TestCases/Linux/kernel-area.cc > > AddressSanitizer-mips-linux :: TestCases/Posix/coverage-direct-large.cc > > Clang :: Driver/cuda-options.cu > > UBSan-ASan-mips :: TestCases/Float/cast-overflow.cpp > > UBSan-Standalone-mips :: TestCases/Float/cast-overflow.cpp > > libc++abi :: backtrace_test.pass.cpp > > libc++abi :: test_demangle.pass.cpp > > I had to kill an excessively long 'llc -march=r600 -mcpu=cypress' process > (>500 > > minutes) to make the tests finish. I assume it's one of those failures. > > > > Tom: Are you aware of any r600 tests that run forever? > > > > Sagar: Could you look into the two ubsan failures? > > Mohit: Could you look into the two asan failures? > > The test system is running 32-bit Debian Jessie for mips (big-endian) and is > a > > MIPS64r2 CPU. You'll need to configure llvm with - > > DLLVM_HOST_TRIPLE=mips-linux-gnu. > > > > > -----Original Message----- > > > From: cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev- > > bounces at cs.uiuc.edu] > > > On Behalf Of Daniel Sanders > > > Sent: 15 July 2015 11:26 > > > To: Hans Wennborg; llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > > > Subject: Re: [cfe-dev] [LLVMdev] [3.7 Release] We have branched > > > > > > Hi, > > > > > > I see there's no rc1 tag yet so I'll try the branch directly with D10715 > (switch > > to > > > cmake) and D6563 (enables directly testing branch with test-release.sh) > > > applied. > > > > > > > -----Original Message----- > > > > From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev- > > > bounces at cs.uiuc.edu] > > > > On Behalf Of Hans Wennborg > > > > Sent: 15 July 2015 01:25 > > > > To: llvmdev; cfe-dev; lldb-dev at cs.uiuc.edu > > > > Subject: [LLVMdev] [3.7 Release] We have branched > > > > > > > > Hi all, > > > > > > > > The 3.7 release branch was created from trunk at r242221 today > (around > > > > 10:40 pm UTC). > > > > > > > > Branch policy: > > > > > > > > - Any doc changes can go in. Updates to the release notes are highly > > > > encouraged, and should be committed directly to the branch. > > > > > > > > - All other patches should be approved by the release manager (me) > and > > > > the appropriate code owner. To get a change merged, commit it to > > > > trunk, and then reply to the commit email with myself and the code > > > > owner cc'd, asking for approval. > > > > > > > > - Fixes to complete existing features may be merged. However, the > > > > features must be completed before Phase II of testing starts, > > > > otherwise they should be disabled. If you recently committed > something > > > > experimental to trunk, please make sure it's disabled on the branch. > > > > > > > > - For any bug fixes that you think might apply to the release branch, > > > > please cc me on the commit message. > > > > > > > > Cheers, > > > > Hans > > > > _______________________________________________ > > > > LLVM Developers mailing list > > > > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > > > > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > > > > > > _______________________________________________ > > > cfe-dev mailing list > > > cfe-dev at cs.uiuc.edu > > > http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
On Wed, Jul 15, 2015 at 10:45 AM, Russell Wallace <russell.wallace at gmail.com> wrote:> Basic test results on Windows 7, visual studio 2013 (64 bit): > > Build clang with visual studio - okay > > Build clang with itself - okay > > Build Python - okay > > Build Ruby - fails on conftest.c, but 3.6 also failed so this is not a > regression bug > > Build Perl - fails. 3.6 also failed, but I think the error message was > different, so this could be a regression bug but hopefully it's actually an > improvement. Current error message: > > cl -c -I. -nologo -GF -W3 -I..\lib\CORE -I.\include -I. -I.. > -DWIN32 -D_CONSOLE -DNO_STRICT -DWIN64 -DCONSERVATIVE > -D_CRT_SECURE_NO_DEPRECATE -D_CRT_NONSTDC_NO_DEPRECATE -DPERLDLL -DPERL_CORE > -O1 -MD -Zi -DNDEBUG -GL -fp:precise -DPERL_TEXTMODE_SCRIPTS > -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS -TP -EHsc -Foperllib.obj > perllib.c > clang-cl.exe: warning: argument unused during compilation: '-GL' > In file included from perllib.c:10: > In file included from ..\lib\CORE\perl.h:3060: > In file included from .\win32thread.h:4: > ./win32.h(284,25) : error: 'selectany' can only be applied to data items > with external linkage >That line is: extern const __declspec(selectany) union { unsigned __int64 __q; double __d; } __PL_nan_u = { 0x7FF8000000000000UI64 }; If it's written like so, clang-cl accepts it: union U { unsigned __int64 __q; double __d; }; extern const __declspec(selectany) U __PL_nan_u = { 0x7FF8000000000000UI64 }; I guess cl.exe applies the declspec to __PL_nan_u while we try to apply it to the type? (Even though it's written before "union", so according to https://msdn.microsoft.com/en-us/library/dabb5z75.aspx it should apply to the variable.) Is there a bug filed for this?> > > On Wed, Jul 15, 2015 at 1:25 AM, Hans Wennborg <hans at chromium.org> wrote: > >> Hi all, >> >> The 3.7 release branch was created from trunk at r242221 today (around >> 10:40 pm UTC). >> >> Branch policy: >> >> - Any doc changes can go in. Updates to the release notes are highly >> encouraged, and should be committed directly to the branch. >> >> - All other patches should be approved by the release manager (me) and >> the appropriate code owner. To get a change merged, commit it to >> trunk, and then reply to the commit email with myself and the code >> owner cc'd, asking for approval. >> >> - Fixes to complete existing features may be merged. However, the >> features must be completed before Phase II of testing starts, >> otherwise they should be disabled. If you recently committed something >> experimental to trunk, please make sure it's disabled on the branch. >> >> - For any bug fixes that you think might apply to the release branch, >> please cc me on the commit message. >> >> Cheers, >> Hans >> _______________________________________________ >> LLVM Developers mailing list >> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >> > > > _______________________________________________ > lldb-dev mailing list > lldb-dev at cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150716/556b1872/attachment.html>