10.0.1-rc1 release has been tagged

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

10.0.1-rc1 release has been tagged

Fangrui Song via cfe-dev
Hi,

I have just tagged the 10.0.1-rc1 release.  Testers can begin testing and uploading
binaries.

If you still want to get a fix into the 10.0.1 release, you still have about a month
to get your fix in.  To request a patch be backported to the release/10.x branch,
file a bug and mark it as a blocker of the release-10.0.1 meta bug.

-Tom

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] 10.0.1-rc1 release has been tagged

Fangrui Song via cfe-dev
On Wed, May 20, 2020 at 3:23 AM Tom Stellard via Release-testers
<[hidden email]> wrote:
>
> Hi,
>
> I have just tagged the 10.0.1-rc1 release.  Testers can begin testing and uploading
> binaries.
>
> If you still want to get a fix into the 10.0.1 release, you still have about a month
> to get your fix in.  To request a patch be backported to the release/10.x branch,
> file a bug and mark it as a blocker of the release-10.0.1 meta bug.

Windows looks good. Uploaded:

$ sha256sum LLVM-10.0.1-rc1-win*.exe
3ca57fc9b80c796a1a68f71a60d94cd5f94818b2b326efaf4e558228565cbecc
LLVM-10.0.1-rc1-win32.exe
ada2f4d596259fad9dd9efa4a14999462feb259dbecd1b7b387539d853f640f3
LLVM-10.0.1-rc1-win64.exe

They were built with the attached batch. file.

 - Hans

_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

build_llvm_1001-rc1._bat_ (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] 10.0.1-rc1 release has been tagged

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
On 20 May 2020, at 03:22, Tom Stellard via Release-testers <[hidden email]> wrote:
>
> I have just tagged the 10.0.1-rc1 release.  Testers can begin testing and uploading
> binaries.
>
> If you still want to get a fix into the 10.0.1 release, you still have about a month
> to get your fix in.  To request a patch be backported to the release/10.x branch,
> file a bug and mark it as a blocker of the release-10.0.1 meta bug.

I have uploaded:

SHA256 (clang+llvm-10.0.1-rc1-amd64-unknown-freebsd11.tar.xz) = 4dbe2041e8aa80ba2b908946052bd4bb20733422707277aa7c297980ed8cd92c
SHA256 (clang+llvm-10.0.1-rc1-i386-unknown-freebsd11.tar.xz) = 5fad007fdabe085de126513875a8e601b1f341889eb36423d2980dd3d34b1d80

but none of the regression tests could run, due to a lit/googletest exception:

llvm-lit: /home/dim/llvm/10.0.1/rc1/llvm-project/llvm/utils/lit/lit/formats/googletest.py:43: warning: unable to discover google-tests in '/home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests': Command '['/home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests', '--gtest_list_tests']' returned non-zero exit status 1.. Process output: b''
Traceback (most recent call last):
  File "/home/dim/llvm/10.0.1/rc1/llvm-project/llvm/utils/lit/lit/formats/googletest.py", line 39, in getGTestTests
    env=localConfig.environment)
  File "/usr/local/lib/python3.7/subprocess.py", line 411, in check_output
    **kwargs).stdout
  File "/usr/local/lib/python3.7/subprocess.py", line 512, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['/home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests', '--gtest_list_tests']' returned non-zero exit status 1.

Running the MLIRSPIRVTests executable shows the actual problem:

$ /home/dim/llvm/10.0.1/rc1/Phase3/Release/llvmCore-10.0.1-rc1.obj/tools/mlir/unittests/Dialect/SPIRV/./MLIRSPIRVTests
Shared object "libc++abi.so.1" not found, required by "MLIRSPIRVTests"

On FreeBSD we use libcxxrt, not libc++abi. Does anybody have an idea why this appears to have changed between 10.0.0 and 10.0.1? And if so, how I tell the build not to link against libc++abi?

-Dimitry


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (230 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [Release-testers] 10.0.1-rc1 release has been tagged

Fangrui Song via cfe-dev
In reply to this post by Fangrui Song via cfe-dev
On Tue, 2020-05-19 at 18:22 -0700, Tom Stellard via Release-testers
wrote:
> Hi,
>
> I have just tagged the 10.0.1-rc1 release.  Testers can begin testing and uploading
> binaries.
>
> If you still want to get a fix into the 10.0.1 release, you still have about a month
> to get your fix in.  To request a patch be backported to the release/10.x branch,
> file a bug and mark it as a blocker of the release-10.0.1 meta bug.
>

Just FYI, the sky seems to have fallen on me here.  I'm not really sure
why it worked before but a lot of parts of clang fail now due to
duplicate registered command-line options.  I will file bugs when I'm
done figuring out all the fixes but giving you an early heads-up.

--
Best regards,
Michał Górny


_______________________________________________
cfe-dev mailing list
[hidden email]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

signature.asc (631 bytes) Download Attachment