llvm dev - Nov 2015 - 3.7.1-rc1 has been tagged. Let's begin testing!

John removed the assertion in his major alignment tracking patch. I
manually did that on the branch in r253380.

On Tue, Nov 17, 2015 at 1:10 PM, Hans Wennborg <hans at chromium.org>
wrote:
> On Mon, Nov 16, 2015 at 7:32 PM, Tom Stellard <tom at stellard.net>
wrote:
> > Hi,
> >
> > I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
> > reminder, when doing regression testing, use the 3.7.0 release
> > as your baseline.
>
> 32-bit Windows looks fine, but I hit an assert during the lit tests
> for 64-bit Windows (below).
>
> Reid, could this be related to your recent merges? Note that while we
> switched the weekly snapshots over to target msvc-style Windows
> recently, 3.7 still targets mingw by default, so the 64-bit build is
> using x86_64-w64-mingw32.
>
>  - Hans
>
>
>
> FAIL: Clang :: CodeGen/libcalls-fno-builtin.c (1715 of 8372)
> ******************** TEST 'Clang :: CodeGen/libcalls-fno-builtin.c'
FAILED
> *****
> ***************
> Script:
> --
> D:/src/llvm_release_build_3.7.1-rc1/build64/./bin/clang.EXE -cc1
> -internal-isyst
> em
> D:\src\llvm_release_build_3.7.1-rc1\build64\bin\..\lib\clang\3.7.1\include
> -n
> ostdsysteminc -S -O3 -fno-builtin -o -
> D:\src\llvm_release_build_3.7.1-rc1\llvm\
> tools\clang\test\CodeGen\libcalls-fno-builtin.c |
> D:/src/llvm_release_build_3.7.
> 1-rc1/build64/./bin\FileCheck.EXE
> D:\src\llvm_release_build_3.7.1-rc1\llvm\tools
> \clang\test\CodeGen\libcalls-fno-builtin.c
> --
> Exit Code: 2
>
> Command Output (stdout):
> --
> Command 0:
"D:/src/llvm_release_build_3.7.1-rc1/build64/./bin/clang.EXE"
> "-cc1"
> "-internal-isystem"
> "D:\src\llvm_release_build_3.7.1-rc1\build64\bin\..\lib\clan
> g\3.7.1\include" "-nostdsysteminc" "-S"
"-O3" "-fno-builtin" "-o" "-"
> "D:\src\ll
>
>
vm_release_build_3.7.1-rc1\llvm\tools\clang\test\CodeGen\libcalls-fno-builtin.c"
>
> Command 0 Result: -2147483645
> Command 0 Output:
>
>
> Command 0 Stderr:
> Assertion failed: !retAI.getIndirectAlign() && "Align unused
on indirect
> return.
> ", file
> D:\src\llvm_release_build_3.7.1-rc1\llvm\tools\clang\lib\CodeGen\CGCall.
> cpp, line 1283
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151117/e5efc793/attachment.html>

On Tue, Nov 17, 2015 at 1:41 PM, Reid Kleckner <rnk at google.com>
wrote:
> John removed the assertion in his major alignment tracking patch. I
manually
> did that on the branch in r253380.
Thanks!

I've uploaded binaries built from that revision to the sftp. sha1sums:
12284e9c8e52c4e3bf025ed2f79d80cbde753a55  LLVM-3.7.1-rc1-win32.exe
3e3f404f8140772154b55daca21e223347175356  LLVM-3.7.1-rc1-win64.exe

These were built and tested with the attached script. (Note that since
I used r253380, this isn't strictly built at the rc1 tag, but I
figured it might be useful to have them anyway.)

Cheers,
Hans
> On Tue, Nov 17, 2015 at 1:10 PM, Hans Wennborg <hans at chromium.org>
wrote:
>>
>> On Mon, Nov 16, 2015 at 7:32 PM, Tom Stellard <tom at
stellard.net> wrote:
>> > Hi,
>> >
>> > I have just tagged 3.7.1-rc1, so it is ready for testing.  As a
>> > reminder, when doing regression testing, use the 3.7.0 release
>> > as your baseline.
>>
>> 32-bit Windows looks fine, but I hit an assert during the lit tests
>> for 64-bit Windows (below).
>>
>> Reid, could this be related to your recent merges? Note that while we
>> switched the weekly snapshots over to target msvc-style Windows
>> recently, 3.7 still targets mingw by default, so the 64-bit build is
>> using x86_64-w64-mingw32.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: build_llvm_371._bat_
Type: application/octet-stream
Size: 2673 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151117/42321747/attachment.obj>

On Tue, Nov 17, 2015 at 06:16:46PM -0800, Hans Wennborg
wrote:
> On Tue, Nov 17, 2015 at 1:41 PM, Reid Kleckner <rnk at google.com>
wrote:
> > John removed the assertion in his major alignment tracking patch. I
manually
> > did that on the branch in r253380.
> 
> Thanks!
> 
> I've uploaded binaries built from that revision to the sftp. sha1sums:
> 12284e9c8e52c4e3bf025ed2f79d80cbde753a55  LLVM-3.7.1-rc1-win32.exe
> 3e3f404f8140772154b55daca21e223347175356  LLVM-3.7.1-rc1-win64.exe
> 
> These were built and tested with the attached script. (Note that since
> I used r253380, this isn't strictly built at the rc1 tag, but I
> figured it might be useful to have them anyway.)
> 
I think we'll probably do an -rc2 then, because there are 2 other
patches I missed that I would like to get in.

-Tom
> Cheers,
> Hans
> 
> > On Tue, Nov 17, 2015 at 1:10 PM, Hans Wennborg <hans at
chromium.org> wrote:
> >>
> >> On Mon, Nov 16, 2015 at 7:32 PM, Tom Stellard <tom at
stellard.net> wrote:
> >> > Hi,
> >> >
> >> > I have just tagged 3.7.1-rc1, so it is ready for testing.  As
a
> >> > reminder, when doing regression testing, use the 3.7.0
release
> >> > as your baseline.
> >>
> >> 32-bit Windows looks fine, but I hit an assert during the lit
tests
> >> for 64-bit Windows (below).
> >>
> >> Reid, could this be related to your recent merges? Note that while
we
> >> switched the weekly snapshots over to target msvc-style Windows
> >> recently, 3.7 still targets mingw by default, so the 64-bit build
is
> >> using x86_64-w64-mingw32.