Re: [lldb-dev] [cfe-dev] Release 13.0.1-rc1 has been tagged
Hi, Uploaded armv7 & aarch64 Ubuntu binaries and also aarch64 Windows: baa53279469e387f333cd90d9e8a30973c8a5d884dd893862435967d40c1a0e9 clang+llvm-13.0.1-rc1-aarch64-linux-gnu.tar.xz 1a523df1cd1a8f64158f602a4e2ce1ad845d322d9dda11225b3d96b2c957203e clang+llvm-13.0.1-rc1-armv7a-linux-gnueabihf.tar.xz 5c363a8e145e4b9985403aa89f496c550ff68423febd350d2a70c0f993b00b29 LLVM-13.0.1-rc1-woa64.zip Same test results as 13.0.0. Cheers, Diana On Tue, 30 Nov 2021 at 07:07, Tom Stellard via cfe-dev < cfe-...@lists.llvm.org> wrote: > Hi, > > I've tagged 13.0.1-rc1. Testers can begin testing and uploading binaries. > > There is still time to submit fixes for the final 13.0.1. I'll give more > details about timelines and how to do this once the bugzilla migration is > complete. Currently, bugzilla is read-only, so we can't submit any fixes > there. > > -Tom > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] 13.0.0-rc3 has been tagged
Hi, I have also uploaded windows on aarch64 (built by Maxim Kuvyrkov): b39a6b72bcd317b58ab67effa9184922515d03c6815850a12be86325f6ec4ef9 LLVM-13.0.0-rc3-woa64.zip Cheers, Diana On Tue, 14 Sept 2021 at 06:40, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > I've tagged 13.0.0-rc3. This will likely be the last rc unless there are > critical bugs that are found. Please test the release and report results. > > -Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] 13.0.0-rc3 has been tagged
Hi, Uploaded armv7 and aarch64 binaries: beadc6b6fab35a46b35f2053b62c8d7c2bcf0b549a789b8ee690fa86fff679a0 clang+llvm-13.0.0-rc3-aarch64-linux-gnu.tar.xz 9ebc21710d94e2a68951295c8df39d952409e125122b97ca77f819565a5afcf3 clang+llvm-13.0.0-rc3-armv7a-linux-gnueabihf.tar.xz No new failures on aarch64. One new failure on armv7: cfi-devirt-lld-armhf :: multiple-inheritance.cpp (I don't think we should block since this isn't the only cfi issue we have; I've added a comment to PR44157). Cheers, Diana On Tue, 14 Sept 2021 at 06:40, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > I've tagged 13.0.0-rc3. This will likely be the last rc unless there are > critical bugs that are found. Please test the release and report results. > > -Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] 13.0.0-rc2 has been tagged
Hi, Uploaded aarch64 & armv7 binaries: 8f692d75f71e89146877bab08760cda98378cc46275b2368b7887a2c605c13c4 clang+llvm-13.0.0-rc2-aarch64-linux-gnu.tar.xz 32148e4790ca2706d19eea7255edd0f99a97a647971cfa05f1b71eecadd7a3ac clang+llvm-13.0.0-rc2-armv7a-linux-gnueabihf.tar.xz Everything looks the same as rc1. Cheers, Diana On Fri, 27 Aug 2021 at 07:20, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > I've tagged the 13.0.0-rc2 release. Testers can begin testing and > uploading > binaries. > > 13.0.0-rc3 is scheduled to be released on Sep. 7, so we'll continue to > accept > bug fixes in the branch until then. > > -Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] LLVM 12.0.0-rc2 has been tagged
Hi, I've uploaded the windows on arm binaries: cc0d601791405bab498b3acfc458f6ba40df4a86e91702f0ce1565bacacf0d77 LLVM-12.0.0-rc2-woa64.exe This was built from the rc2 source snapshot without any patches on top \o/ Credit goes to my colleague Maxim Kuvyrkov for producing and testing the binaries. Cheers, Diana On Wed, 24 Feb 2021 at 05:45, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > LLVM 12.0.0-rc2 has been tagged. Please test and report any issues in > bugzilla. > > -Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] LLVM 11.1.0-final has been tagged.
Hi,
Uploaded arm & aarch64:
18df38247af3fba0e0e2991fb00d7e3cf3560b4d3509233a14af699ef0039e1c
clang+llvm-11.1.0-aarch64-linux-gnu.tar.xz
18a3c3aedf1181aa18da3f5d0a2c67366c6d5fb398ac00e461298d9584be5c68
clang+llvm-11.1.0-armv7a-linux-gnueabihf.tar.xz
Same failures as before + a new one on armv7:
Profile-armhf :: Posix/gcov-fork.c
I haven't seen this in any of the previous release candidates, not sure
what's going on there (log attached, we'll probably only open a bug report
if we see it in llvm 12 as well).
Cheers,
Diana
On Thu, 18 Feb 2021 at 05:06, Tom Stellard via cfe-dev <
cfe-...@lists.llvm.org> wrote:
> Hi,
>
> I've tagged 11.1.0-final, testers may begin uploading binaries now.
>
> -Tom
>
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
FAIL: Profile-armhf :: Posix/gcov-fork.c (64525 of 68157)
TEST 'Profile-armhf :: Posix/gcov-fork.c' FAILED
Script:
--
: 'RUN: at line 8'; mkdir -p
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/Phase3/Release/llvmCore-11.1.0-final.obj/projects/compiler-rt/test/profile/Profile-armhf/Posix/Output/gcov-fork.c.tmp.d
&& cd
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/Phase3/Release/llvmCore-11.1.0-final.obj/projects/compiler-rt/test/profile/Profile-armhf/Posix/Output/gcov-fork.c.tmp.d
: 'RUN: at line 9';
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/Phase3/Release/llvmCore-11.1.0-final.obj/./bin/clang
-ldl --coverage
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/llvm-project/compiler-rt/test/profile/Posix/gcov-fork.c
-o
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/Phase3/Release/llvmCore-11.1.0-final.obj/projects/compiler-rt/test/profile/Profile-armhf/Posix/Output/gcov-fork.c.tmp
: 'RUN: at line 10'; test -f gcov-fork.gcno
: 'RUN: at line 12'; rm -f gcov-fork.gcda &&
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/Phase3/Release/llvmCore-11.1.0-final.obj/projects/compiler-rt/test/profile/Profile-armhf/Posix/Output/gcov-fork.c.tmp
: 'RUN: at line 13'; llvm-cov gcov -t gcov-fork.gcda | FileCheck
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/llvm-project/compiler-rt/test/profile/Posix/gcov-fork.c
--
Exit Code: 1
Command Output (stderr):
--
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/llvm-project/compiler-rt/test/profile/Posix/gcov-fork.c:18:32:
error: CHECK-NEXT: expected string not found in input
void func2() {} // CHECK-NEXT: 2: [[#@LINE]]:
^
:22:21: note: scanning from here
1: 17:void func1() {} // CHECK: 1: [[#@LINE]]:void func1()
^
:22:21: note: with "@LINE" equal to "18"
1: 17:void func1() {} // CHECK: 1: [[#@LINE]]:void func1()
^
:23:39: note: possible intended match here
1: 18:void func2() {} // CHECK-NEXT: 2: [[#@LINE]]:
^
Input file:
Check file:
/home/tcwg-buildslave/workspace/tcwg-llvm-release/tcwg-tk1_32-build/final/llvm-project/compiler-rt/test/profile/Posix/gcov-fork.c
-dump-input=help explains the following input dump.
Input was:
<<
.
.
.
17: -: 12:// RUN: rm -f gcov-fork.gcda && %run %t
18: -: 13:// RUN: llvm-cov gcov -t gcov-fork.gcda | FileCheck %s
19: -: 14:
20: -: 15:#include
21: -: 16:
22: 1: 17:void func1() {} // CHECK: 1: [[#@LINE]]:void func1()
next:18'0 X~~
error: no match found
23: 1: 18:void func2() {} // CHECK-NEXT: 2: [[#@LINE]]:
next:18'0
next:18'1 ? possible
intended match
24: 1: 19:int main(void) { // CHECK-NEXT: 1: [[#@LINE]]:
next:18'0 ~
25: 1: 20: func1(); // CHECK-NEXT: 1: [[#@LINE]]:
next:18'0 ~~
26: 1: 21: if (fork() == -1) return 1; // CHECK-NEXT: 1: [[#@LINE]]:
next:18'0 ~
27: 1: 22: func2(); // CHECK-NEXT: 2: [[#@LINE]]:
next:18'0 ~~
28: 1: 23: return 0; // CHECK-NEXT: 2: [[#@LINE]]:
next:18'0 ~~~
29: 1: 24:}
next:18'0
>>
--
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] 12.0.0-rc1 Release has been tagged
Hello,
I've uploaded binaries for Windows on Arm:
081373cc76e88224020fea42eba2161d972f03bb83ebc055fb3cd4f2cfcdfb95
LLVM-12.0.0-rc1-woa64.exe
It was built from the current release/12.x branch (commit b46924ee) with
two patches applied on top:
- https://reviews.llvm.org/D96259
- https://reviews.llvm.org/D96498
It contains "clang;clang-tools-extra;lld;compiler-rt” projects.
Compiler-RT has sanitizers disabled (MEMPROF and XRAY use sanitizer
infrastucture). I.e.,
===
+ -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;compiler-rt" ^
+ -DCOMPILER_RT_BUILD_SANITIZERS=OFF ^
+ -DCOMPILER_RT_BUILD_MEMPROF=OFF ^
+ -DCOMPILER_RT_BUILD_XRAY=OFF ^
===
I've attached the changes we had to make to
llvm/utils/releases/build_llvm_package.bat. @Maxim Kuvyrkov is going to
clean them up and post a patch in the next couple of weeks (he's been doing
all the hard work, I'm just uploading).
This is the first time we're trying to provide a release for Windows on
Arm, so if anyone has any comments or questions, feel free to send an email
:)
Cheers,
Diana
On Thu, 28 Jan 2021 at 05:05, Tom Stellard via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi,
>
> I've tagged the 12.0.0-rc1 release. Testers can begin testing and upload
> binaries.
>
> -Tom
>
> ___
> lldb-dev mailing list
> lldb-dev@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
diff --git a/llvm/utils/release/build_llvm_package.bat b/llvm/utils/release/build_llvm_package.bat
index 35dcd9f613c4..8d083f1985df 100755
--- a/llvm/utils/release/build_llvm_package.bat
+++ b/llvm/utils/release/build_llvm_package.bat
@@ -19,14 +19,18 @@ REM https://github.com/swig/swig/issues/769
REM You need to modify the paths below:
-set vsdevcmd=C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\Tools\VsDevCmd.bat
+set vsdevcmd=C:\BuildTools\Common7\Tools\VsDevCmd.bat
set python32_dir=C:\Users\%USERNAME%\AppData\Local\Programs\Python\Python36-32
set python64_dir=C:\Users\%USERNAME%\AppData\Local\Programs\Python\Python36
+set 7z=C:\Program Files\7-Zip\7z
+
for /f "usebackq" %%i in (`PowerShell ^(Get-Date^).ToString^('MMdd'^)`) do set datestamp=%%i
set revision=%1
+git -C C:\Users\%USERNAME%\source\llvm-project remote update -p
+for /f "usebackq" %%i in (`git -C C:\Users\%USERNAME%\source\llvm-project rev-parse refs/remotes/origin/release/12.x`) do set revision=%%i
set package_version=12.0.0-%revision:~0,8%
set clang_format_vs_version=12.0.0.%datestamp%
set build_dir=llvm_package_%revision:~0,8%
@@ -36,15 +40,20 @@ echo Package version: %package_version%
echo Clang format plugin version: %clang_format_vs_version%
echo Build dir: %build_dir%
echo.
-pause
+REM pause
mkdir %build_dir%
cd %build_dir%
echo Checking out %revision%
-curl -L https://github.com/llvm/llvm-project/archive/%revision%.zip -o src.zip || exit /b
-7z x src.zip || exit /b
-mv llvm-project-* llvm-project || exit /b
+git clone --single-branch --branch release/12.x --reference C:\Users\%USERNAME%\source\llvm-project https://github.com/llvm/llvm-project.git || exit /b
+git -C llvm-project fetch origin 71c29b4cf3fb2b5610991bfbc12b8bda97d60005 || exit /b
+git -C llvm-project cherry-pick FETCH_HEAD || exit /b
+git -C llvm-project fetch C:\Users\%USERNAME%\source\llvm-project refs/heads/exegesis-fix || exit /b
+git -C llvm-project cherry-pick FETCH_HEAD || exit /b
+REM curl -L https://github.com/llvm/llvm-project/archive/%revision%.zip -o src.zip || exit /b
+REM %7z% x src.zip || exit /b
+REM mv llvm-project-* llvm-project || exit /b
REM Setting CMAKE_CL_SHOWINCLUDES_PREFIX to work around PR27226.
set cmake_flags=^
@@ -53,51 +62,61 @@ set cmake_flags=^
-DLLVM_INSTALL_TOOLCHAIN_ONLY=ON ^
-DLLVM_BUILD_LLVM_C_DYLIB=ON ^
-DCMAKE_INSTALL_UCRT_LIBRARIES=ON ^
- -DCLANG_FORMAT_VS_VERSION=%clang_format_vs_version% ^
-DPACKAGE_VERSION=%package_version% ^
- -DLLDB_RELOCATABLE_PYTHON=1 ^
- -DLLDB_TEST_COMPILER=%cd%\build32_stage0\bin\clang.exe ^
-DCMAKE_CL_SHOWINCLUDES_PREFIX="Note: including file: " ^
- -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld;compiler-rt;openmp;lldb"
+ -DLLVM_DEFAULT_TARGET_TRIPLE=aarch64-windows-msvc ^
+ -DLLVM_HOST_TRIPLE=aarch64-windows-msvc ^
+ -DLLVM_TARGET_ARCH=AArch64
REM TODO: Run the "check-all" tests.
set "VSCMD_START_DIR=%CD%"
-call "%vsdevcmd%" -arch=x86
-set CC=
-set CXX=
+call "%vsdevcmd%" -host_arch=x86 -arch=arm64
+set "PATH=C:\Users\%USERNAME%\source\llvm-package\bin;C:\Users\%USERNAME%\source\ninja;%PATH%;C:\msys32\usr\bin;C:\Program Files (x86)\NSIS"
+set CC=clang-cl
+set CXX=clang-cl
mkdir build32_stage0
cd build32_stage0
-cmake -GNinja %cmake_flags% -DPYTHON_HOME=%python32_dir% -DPYTHON_EXECUTABLE=%python32_dir%\python.exe ..\llvm-project\llvm || exit /b
+cmake -GNinja %cmake_flags% ^
+ -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;lld" ^
+ -DLLVM_TARGETS_TO_BUILD="AArch64" ^
+ ..\llvm-project\llvm || exit /b
ninja all ||
Re: [lldb-dev] [Release-testers] LLVM 11.1.0-rc3 has been tagged
Hi, Arm & AArch64 are ready: 0a164b850d1b6cb9924f93e738693bc672b962160adc6d88eb40d0fed0226e4f clang+llvm-11.1.0-rc3-aarch64-linux-gnu.tar.xz 84b61009a8c1f1f2ca6d32ed893988791a654516782fb20815172da09770 clang+llvm-11.1.0-rc3-armv7a-linux-gnueabihf.tar.xz armv7 looks the same as previous rc's. On aarch64 I got these failures, which are intermittent, so we needn't block the release on them: AddressSanitizer-aarch64-linux :: TestCases/Posix/waitid.cpp AddressSanitizer-aarch64-linux-dynamic :: TestCases/Posix/waitid.cpp (haven't seen this in the past, but looks just like the one above) lit :: googletest-timeout.py Cheers, Diana On Mon, 8 Feb 2021 at 18:15, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > I've tagged LLVM 11.1.0-rc3. If there are no issues, then I'll be tagging > the final release in 1 week. Testers please test and upload binaries. > > -Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] Attn Buildbot Owners: Would you like your builder to test the release branch?
Hi Tom, This sounds interesting! Would this also make it possible to automatically get the release binaries from the buildbots, as opposed to manually uploading to the FTP server? Cheers, Diana On Tue, 2 Feb 2021 at 01:46, Tom Stellard via cfe-dev < cfe-...@lists.llvm.org> wrote: > Hi, > > I would like to improve the testing coverage in the release branch, so if > you > are a buildbot owner and would like to enable your builder for the release > branch, > let me know, and I can help get it enabled. > > Also, if you have any ideas for some more extensive testing that might be > too > slow to run on the main branch, we may be able to enable it on the release > branch either running once per commit or once per tag. > > Thanks, > Tom > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] LLVM 11.1.0-rc1 has been tagged
Hi, Arm & AArch64 are ready: b9a8e8669004b34660d39f1f0acf37a6f33e25876c8d37dc0389c8df4a7e811c clang+llvm-11.1.0-rc1-aarch64-linux-gnu.tar.xz 241fafdd18b2557106bb430c7f69b4973a935ec23b469f9582a061794e1cd1ef clang+llvm-11.1.0-rc1-armv7a-linux-gnueabihf.tar.xz No new failures. Cheers, Diana On Thu, 14 Jan 2021 at 02:46, Tom Stellard via Release-testers < release-test...@lists.llvm.org> wrote: > Hi, > > LLVM 11.1.0-rc1 has been tagged. This is a special release with a > libclang.so ABI fix to ensure libclang.so remains compatible with LLVM > 10 and LLVM 12. Testers may begin testing and upload binaries. > > Thanks, > Tom > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] LLVM 11.0.1-rc2 has been tagged
Hi, I've uploaded Arm & AArch64: 7b0bb1b5b4d3f31ea32bc1d8a169528e3ca851308f03431d4ce06a6b4a0657e7 clang+llvm-11.0.1-rc2-aarch64-linux-gnu.tar.xz 7afd6d24a5348af2f1f756858c77dd4e055161fb51e3a19f074ad2d81caeff7f clang+llvm-11.0.1-rc2-armv7a-linux-gnueabihf.tar.xz No regressions. Cheers, Diana On Tue, 5 Jan 2021 at 10:32, Michał Górny via lldb-dev < lldb-dev@lists.llvm.org> wrote: > On Mon, 2021-01-04 at 19:19 -0800, Tom Stellard wrote: > > On 12/21/20 11:51 AM, Michał Górny wrote: > > > On Fri, 2020-12-18 at 22:33 -0800, Tom Stellard via Release-testers > > > wrote: > > > > Hi, > > > > > > > > I've just tagged LLVM 11.0.1-rc2, hopefully this will be the last > > > > release candidate. Testers can begin testing and uploading binaries. > > > > > > Gentoo amd64 looks good-ish, except that: > > > > > > 1) compiler-rt LSAN seems entirely broken, ThreadDescriptorSize tests > > > fail too -- I guess once again glibc upgrade broke it. > > > > > > > Is this a regression compared with -rc1 ? > > No. I'm sorry, I thought that was clear from the last sentence. > > > > > -Tom > > > > > 2) LLDB tests are broken as usual -- but I'm finally starting to work > > > on them. > > > > > > > -- > Best regards, > Michał Górny > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [Release-testers] LLVM 11.0.1-rc1 has been tagged
Hi, I've uploaded binaries for armv7 & aarch64. No regressions compared to 11.0.0. 73c25494b8632a8969504522d2fc444118768e129e8307920b7fa9cdd7c70649 clang+llvm-11.0.1-rc1-aarch64-linux-gnu.tar.xz 2e0244f55914383767f6ce9ef745ba9040beab82a71d430ff0844ef58993e504 clang+llvm-11.0.1-rc1-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Fri, 4 Dec 2020 at 01:01, Bernhard Rosenkraenzer via cfe-dev < cfe-...@lists.llvm.org> wrote: > On Thursday, November 26, 2020 08:21 CET, Tom Stellard via Release-testers > wrote: > > > Hi, > > > > I've tagged LLVM 11.0.1-rc1. > > Hi, > I've updated OpenMandriva and rebuilt all packages, no regressions from > 11.0.0 detected on all arches. > > ttyl > bero > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [llvm-dev] [11.0.0 Release] Release Candidate 6 is here
Hi, Uploaded Arm & AArch64: 95449841c1c4b0164414e58b1053a3877e3bd73d9b1b3e15e5d1d4c2fd5cae1e clang+llvm-11.0.0-rc6-aarch64-linux-gnu.tar.xz 40ba7c35c5430cc2775b8dbf0bc4687d7a466c29332b89193de903ea4557fb05 clang+llvm-11.0.0-rc6-armv7a-linux-gnueabihf.tar.xz Same as previous rc's. Cheers, Diana On Sat, 10 Oct 2020 at 04:46, Shoaib Meenai via cfe-dev wrote: > > Uploaded macOS binaries to > https://drive.google.com/file/d/1OVsImFG99a0jNOWc1IDhRvER3CvbGmFp/view?usp=sharing. > > The SHA-256 is: > > b35f3b6ce4de703f015bdf9d936f530b28c752737c2dd60715bd3d098787652b > clang+llvm-11.0.0-rc6-x86_64-apple-darwin.tar.xz > > The full test results are: > > Failed Tests (2): > libunwind :: libunwind_01.pass.cpp > libunwind :: signal_frame.pass.cpp > > Testing Time: 3211.12s > Unsupported : 3200 > Passed : 68254 > Expectedly Failed: 264 > Failed : 2 > > The libunwind tests failed with rc5 and also fail for 10.0.1 on my machine, > so it's likely an environmental issue. (See > https://lists.llvm.org/pipermail/llvm-dev/2020-October/145513.html for my > previous investigation into the libunwind failures, where we determined they > shouldn't be launch-blocking.) > > (It might be easier to give me SFTP access, to save Tobias the trouble of > having to download and reupload to the SFTP.) > > On 10/7/20, 7:40 AM, "llvm-dev on behalf of Hans Wennborg via llvm-dev" > wrote: > > Hello once again, > > A few more issues appeared, so here is yet another release candidate: > llvmorg-11.0.0-rc6 was just tagged. > > Source code and docs are available at > https://prereleases.llvm.org/11.0.0/#rc6 > and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc6 > > Pre-built binaries will be added as they become ready. > > Please file reports for any bugs you find as blockers of > https://llvm.org/pr46725 > > Release testers, if you still have cycles, please take this for a > quick spin. The changes from rc5 are minimal, and hopefully we can tag > this as the final version very soon now. > > Thanks, > Hans > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [flang-dev] [llvm-dev] [11.0.0 Release] Release Candidate 4 is here
Hi, Uploaded arm & aarch64: 3e2dbe0dcdaa82aaba4480c9b5d042846858903bff743259a1b63a36c75ba9d7 clang+llvm-11.0.0-rc4-armv7a-linux-gnueabihf.tar.xz 8fa05ddb6fe4e49c4347f3decdbcaa623f3b0e88fc6a264058f05fc0ed3d71e0 clang+llvm-11.0.0-rc4-aarch64-linux-gnu.tar.xz No new regressions. Cheers, Diana On Wed, 30 Sep 2020 at 20:24, Amy Kwan via flang-dev wrote: > > Hi Hans, > > I've completed release testing for llvm-11.0.0-rc4 on Power PC 64bit Little > Endian for Ubuntu 18.04 and Red Hat 7.4. I did not see any regressions for > RC4. > I have uploaded the respective binaries and have attached the sha1 files. > > Thank you, > Amy K. > > On Mon, 28 Sep 2020 at 13:28, Hans Wennborg via llvm-dev > wrote: >> >> Hello everyone, >> >> A little less than a week after rc3, the llvmorg-11.0.0-rc4 tag was >> just created. >> >> Source code and docs are available at >> https://prereleases.llvm.org/11.0.0/#rc4 >> and >> https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc4 >> >> Pre-built binaries will be added as they become ready. >> >> Please file bug reports for any issues you find as blockers of >> https://llvm.org/pr46725 >> >> Release testers: if you still have cycles, please run the test script, >> share your results, and upload binaries. And thank you very much for >> your help so far. >> >> This is very similar to rc3, but picks up a few more fixes. Again, >> there are currently no open release blockers, which means this is what >> the final release could look like. >> >> Thanks, >> Hans >> ___ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > ___ > flang-dev mailing list > flang-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/flang-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] 10.0.1-rc1 release has been tagged
Hi, Uploaded binaries for ARM & AArch64: e7cdf76722c9f5b90ec3f5d0e6cf5545badc6a7eaf8477b764a25845aee9a844 clang+llvm-10.0.1-rc1-aarch64-linux-gnu.tar.xz a11427f38283a522a22f4799c40518b09b72bdd4170ecb456544b459f74d1fc3 clang+llvm-10.0.1-rc1-armv7a-linux-gnueabihf.tar.xz AArch64 is green (yay! IIRC 10.0.0 had an issue). For ARM we still have PR44157 & PR44158 (which we also had for llvm 10.0.0), and I have also opened PR46092 and PR46093 for some new failures. I'll try to have a quick look to see if they're environment problems or if we can bisect them. Cheers, Diana On Mon, 25 May 2020 at 23:31, Michał Górny via Release-testers < release-test...@lists.llvm.org> wrote: > 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. > > > > Ok, it turns out my issues were due to py3.7+. I've requested > backporting one lit patch and with it, there are no new regressions. > > However, it made me notice that some clangd unittest are failing to > execute with duplicate command-line option errors but the errors are > ignored by lit. It happens when clang is linked to dylib, and it is > non-trivial to fix and I'm not sure if I'll be able to fix it myself. > Any and all help appreciated. > > I've tried to see if it is fixed in master but I can't seem to manage to > find a recent clang revision that wouldn't segfault all the way. > > -- > Best regards, > Michał Górny > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] LLVM 9.0.1-final has been tagged
Hi, Uploaded ARM & AArch64, both look the same as before. 84023d5309646e1f56beed056ab7d7ecf92d03b26e87917deb8e7fc191805d15 clang+llvm-9.0.1-aarch64-linux-gnu.tar.xz 91638613913537f8c0c84a59f59f00fafeafb6b189164cae471d4e3bccaf1df3 clang+llvm-9.0.1-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Fri, 20 Dec 2019 at 05:07, Tom Stellard via cfe-dev < cfe-...@lists.llvm.org> wrote: > Hi, > > I've just tagged the 9.0.1-final release. Testers can begin uploading > binaries. > > -Tom > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLVM 9.0.1-rc3 has been tagged
Hi, Uploaded arm & aarch64. Both look the same as rc2. c8b39289e8d8ef80b44fabd5f8f508a2fec4dcc099dee0ae3f625e491f9b1cbc clang+llvm-9.0.1-rc3-armv7a-linux-gnueabihf.tar.xz 36d165195adb58bacf463e3659ebfa4350342867d7679bedf2734d2b326b4cfd clang+llvm-9.0.1-rc3-aarch64-linux-gnu.tar.xz Sorry about the delay. Diana On Sat, 14 Dec 2019 at 07:34, Tom Stellard via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi, > > I've just tagged LLVM 9.0.1-rc3. Testers can begin testing and uploading > binaries. This will be the last release candidate unless there is a > major problem. I'm planning to tag the final release on Dec 19. > > -Tom > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] LLVM 9.0.1-rc2 has been tagged
Hi, Uploaded ARM & AArch64: b0e4160da05a2a734cc2e73b925003a7595798f9544c522fa3e3e5815451b861 clang+llvm-9.0.1-rc2-aarch64-linux-gnu.tar.xz 2c5c08fd4a5fb290d3f148b806bb708832239030fe39529746de3e746bbf5cdd clang+llvm-9.0.1-rc2-armv7a-linux-gnueabihf.tar.xz Same as rc1. Cheers, Diana On Sat, 7 Dec 2019 at 04:03, Tom Stellard via llvm-dev wrote: > > Hi, > > I've tagged LLVM 9.0.1-rc2. Testers can begin testing and uploading binaries. > If all goes well, this will be the last -rc. > > -Tom > > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] LLVM 9.0.1-rc1 Release has been tagged
Hi, Uploaded ARM & AArch64: 710a028f99b14d118cfb676ff6f74de1911945a49e5a38d727b41db21e6098a1 clang+llvm-9.0.1-rc1-aarch64-linux-gnu.tar.xz 43c3710f92214408dcebadc41e460b20b64a2228a45f25fab94b1fac2e2f62dd clang+llvm-9.0.1-rc1-armv7a-linux-gnueabihf.tar.xz AArch64 seems OK, but we get some test failures on ARM: https://bugs.llvm.org/show_bug.cgi?id=44157 https://bugs.llvm.org/show_bug.cgi?id=44158 Cheers, Diana On Sat, 23 Nov 2019 at 07:20, Tom Stellard via cfe-dev wrote: > > Hi, > > I've tagged the LLVM 9.0.1-rc1 release. Testers can begin testing and upload > binaries. I've also updated the test-release.sh script to pull from GitHub > instead of SVN, if you run into any issues with the new script, let me know. > > -Tom > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] RFC: Using GitHub Actions for CI testing on the release/* branches
Hi Tom, This sounds very interesting! +1 from me. What does this imply for the release testers? Would it be possible / desirable for us to add self-hosted runners for other architectures? I'm assuming GitHub only provides x86, right? I totally missed any details about that in their docs, but it seems to be implied here [1]. I'm not saying we should go all-possible-arches from the start, we can definitely try it out only for x86 this time around if you think that would be the best approach. Thanks, Diana [1] https://github.blog/2019-11-05-self-hosted-runners-for-github-actions-is-now-in-beta/ On Tue, 12 Nov 2019 at 10:33, James Henderson via lldb-dev wrote: > > Although I've not had any Github Action experience, and despite being one who > has raised objections to other parts of adopting github features, this sounds > like a sensible idea. It seems odd to me that we don't already have some form > of CI for our releases, so anything that improves on that is great. > > James > > On Tue, 12 Nov 2019 at 00:34, David Blaikie via lldb-dev > wrote: >> >> Not having given it deep thought/analysis, nor understanding much of the GIT >> infrastructure here, but: Sounds good to me, for whatever that's worth :) >> >> On Mon, Nov 11, 2019 at 4:32 PM Tom Stellard via llvm-dev >> wrote: >>> >>> Hi, >>> >>> I would like to start using GitHub Actions[1] for CI testing on the >>> release/* >>> branches. As far as I know we don't have any buildbots listening to the >>> release branches, and I think GitHub Actions are a good way for us to >>> quickly >>> bring-up some CI jobs there. >>> >>> My proposal is to start by adding two post-commit CI jobs to the >>> release/9.x branch. >>> One for building and testing (ninja checka-all) llvm/clang/lld on Linux, >>> Windows, and Mac, and another for detecting ABI changes since the 9.0.0 >>> release. >>> >>> I have already implemented these two CI jobs in my llvm-project fork on >>> GitHub[2][3], >>> but in order to get these running in the main repository, I would need to: >>> >>> 1. Create a new repository in the LLVM organization called 'actions' for >>> storing some custom >>> builds steps for our CI jobs (see [4]). >>> 2. Commit yaml CI definitions to the .github/workflows directory in the >>> release/9.x >>> branch. >>> >>> In the future, I would also like to add buil and tests jobs for other >>> sub-projects >>> once I am able to get those working. >>> >>> In addition to being used for post-commit testing, having these CI >>> definitions in the >>> main tree will make it easier for me (or anyone) to do pre-commit testing >>> for the >>> release branch in a personal fork. It will also allow me to experiment >>> with some new >>> workflows to help make managing the releases much easier. >>> >>> I think this will be a good way to test Actions in a low traffic >>> environment to >>> see if they are something we would want to use for CI on the master branch. >>> >>> Given that we are close to the end of the 9.0.1 cycle, unless there are any >>> strong objections, I would like to get this enabled by Mon Nov 18, to >>> maximize its >>> usefulness. Let me know what you think. >>> >>> Thanks, >>> Tom >>> >>> [1] https://github.com/features/actions >>> [2] >>> https://github.com/tstellar/llvm-project/commit/952d80e8509ecc95797b2ddbf1af40abad2dcf4e/checks?check_suite_id=305765621 >>> [3] >>> https://github.com/tstellar/llvm-project/commit/6d74f1b81632ef081dffa1e0c0434f47d4954423/checks?check_suite_id=303074176 >>> [4] https://github.com/tstellar/actions >>> >>> ___ >>> LLVM Developers mailing list >>> llvm-...@lists.llvm.org >>> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] [cfe-dev] Mailing list changes this week
Hi,
Is this monotonic incrementing identifier part of the email? I think
it would really complicate buildbot maintenance if we didn't have it
in obvious places. For instance, we have a (hacky) monitoring page for
our ARM/AArch64 buildbots [1] and it really helps a lot to just look
at the commit range for the last build to know if a fix actually
worked or not ("is the fix commit in that range? if not wait a bit
more before investigating"). Using just a git hash and having to
manually count commits would be a waste of time.
Just my 2c,
Diana
[1] http://llvm.validation.linaro.org/
On Wed, 16 Oct 2019 at 07:42, Shoaib Meenai via llvm-dev
wrote:
>
> I thought we were just going to count commits on a particular branch and use
> the (branch name, commit count) tuple as our monotonic incrementing
> identifier?
> https://llvm.org/docs/Proposals/GitHubMove.html#on-managing-revision-numbers-with-git
>
>
>
>
>
> From: cfe-dev on behalf of cfe-dev
>
> Organization: Red Hat
> Reply-To: "tstel...@redhat.com"
> Date: Tuesday, October 15, 2019 at 10:13 PM
> To: Mehdi AMINI
> Cc: llvm-dev , cfe-dev ,
> "openmp-dev (openmp-...@lists.llvm.org)" , LLDB
> Dev
> Subject: Re: [cfe-dev] Mailing list changes this week
>
>
>
> On 10/15/2019 09:44 PM, Mehdi AMINI wrote:
>
> On Tue, Oct 15, 2019 at 9:33 PM Tom Stellard > wrote:
>
> On 10/15/2019 09:24 PM, Mehdi AMINI wrote:
>
> > Hi Tom.
>
> >
>
> > One issue with this is that we don't have a clear "ordering" from
> linear revision numbers from these emails. Have we looked into continuing to
> generate our own emails per commits instead so that we control the format?
>
> >
>
> This actually what we are doing, we are listening for github commit
> events and
>
> then generating our own emails based on the data in the event. We can
> format
>
> the emails how ever we want, and we tried to match the current SVN
> format exactly.
>
> Ah great!
>
>
>
> Is the some other information you would like to have in the emails to
> show the
>
> ordering?
>
> The only thing I was looking to get was to continue to have a monotonic
> incrementing integer for the revision instead of the git hash alone: I don't
> know if `git llvm` has this feature yet but this was discussed a while ago (I
> don't remember if we just mentioned counting the commits in the repo from the
> beginning or using an invocation of `git describe` or something derived).
>
>
>
> We talked about using `git describe` for this, but this would require that we
>
> add tags to the master branch each time the version number was bumped. We
>
> discussed this[1] last year, but deferred the decision, since we couldn't get
>
> consensus on the tag name.
>
>
>
> -Tom
>
>
>
> [1]
> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.llvm.org_pipermail_llvm-2Ddev_2018-2DDecember_128484.html&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=o3kDXzdBUE3ljQXKeTWOMw&m=_SmpuqSzuAhMoF3exJmWRp6KnerIOE6WdU4kcv3tjhQ&s=p_75z-WV3dFcBRoqs2YeTexKxeCf8oyS-atIo6wG6Fg&e=
>
>
>
> --
>
> Mehdi
>
>
>
> -Tom
>
> > Thanks,
>
> >
>
> > --
>
> > Mehdi
>
> >
>
> >
>
> >
>
> > On Tue, Oct 15, 2019 at 9:07 PM Tom Stellard via cfe-dev
> mailto:cfe-...@lists.llvm.org>
> >> wrote:
>
> >
>
> > Hi,
>
> >
>
> > We are going to start to switching from SVN commit emails to
> GitHub commit
>
> > emails this week. The only real change you should notice is that
>
> > the revision number in the subject will be replaced with a git
> hash and
>
> > the diff links in the email will point to GitHub. Otherwise the
>
> > content and format of the email should be the same.
>
> >
>
> > We are going to start by rolling this out for the openmp-commits
> list
>
> > and then once that's working begin migrating the rest of the
> lists. If you
>
> > notice any issues with the new emails, please file a bug and mark
> it
>
> > as a blocker of the github meta-bug (llvm.org/PR39393
> >
> >).
>
> >
>
> > Thanks,
>
> > Tom
>
> > ___
>
> > cfe-dev mailing list
>
> > cfe-...@lists.llvm.org
> >
>
> >
> https://urldefense.proofpoint.com/v2/url?u=htt
Re: [lldb-dev] [Release-testers] [9.0.0 Release] Release Candidate 6 is here
Hi, Uploaded f8f3e6bdd640079a140a7ada4eb6f5f05aeae125cf54b94d44f733b0e8691dc2 clang+llvm-9.0.0-aarch64-linux-gnu.tar.xz ff6046bf98dbc85d7cb0c3c70456bc002b99a809bfc115657db2683ba61752ec clang+llvm-9.0.0-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Thu, 19 Sep 2019 at 16:56, Hans Wennborg via Release-testers wrote: > > On Tue, Sep 17, 2019 at 4:05 PM Hans Wennborg wrote: > > > > Hello everyone, > > > > 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In > > the Git monorepo, it's tagged as llvmorg-9.0.0-rc6. > > This has now been tagged as the final 9.0.0 release. In the Git > monorepo, it's tagged as llvmorg-9.0.0. > > The official release announcement will follow as soon as the source > tarballs and docs are ready on the web page. > > Testers: please start building the final binaries, and I'll add them > as they become ready. > > Many thanks for your hard work! > Hans > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [9.0.0 Release] Release Candidate 6 is here
Hi, Same as before. b70d9b0f83ea0df0d59f54445930110f9d7819afd46dd1824853d9cf92ff2164 clang+llvm-9.0.0-rc6-armv7a-linux-gnueabihf.tar.xz 6be0e426f2ecaefb38813321d467746eb67b1f736024dde46eb1500b49d4af91 clang+llvm-9.0.0-rc6-aarch64-linux-gnu.tar.xz Cheers, Diana On Tue, 17 Sep 2019 at 16:05, Hans Wennborg via lldb-dev wrote: > > Hello everyone, > > 9.0.0-rc6 was just tagged from the release_90 branch at r372100. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc6. > > Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc6 > > This is the same as rc5 plus one very minor change (r371969) that > still seemed good to pick up. > > I'm not allocating extra time for testing this one, expecting to tag > 'final' in a day or two unless any new problem arises. If you still > have cycles to spare, testing is still very much appreciated of > course. > > As usual, please file bug reports about any issues you find, marking > them blocking of https://llvm.org/PR42474 > > Thanks, > Hans > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [libcxx-dev] [9.0.0 Release] Release Candidate 5 is here
Hi, Uploaded ARM & AArch64: 09dc9f7401419aea8b3c157f99c9610beb193461b4ef4626ea0a7424ab218e3e clang+llvm-9.0.0-rc5-armv7a-linux-gnueabihf.tar.xz e04c2e34b2feafe4fd34cf1fe36af73d27fa414ff2a8e038da0f6eed2c6c8f00 clang+llvm-9.0.0-rc5-aarch64-linux-gnu.tar.xz They both seem ok. Cheers, Diana On Fri, 13 Sep 2019 at 14:06, Hans Wennborg via libcxx-dev wrote: > > Hello everyone, > > 9.0.0-rc5 was just tagged from the release_90 branch at r371837. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc5. > > Source code and docs are available at > https://prereleases.llvm.org/9.0.0/#rc5 Binaries will be added as they > become available. > > There is only a single change from rc4 to rc5. Once more, the hope is > that this will be the last release candidate and that we can tag the > final release soon. > > Please file bug reports for any issues you find, marking them blocking > of https://llvm.org/PR42474 > > Release testers, please run the test script and share your results. > > Thanks, > Hans > ___ > libcxx-dev mailing list > libcxx-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [libcxx-dev] [9.0.0 Release] Release Candidate 4 is here
Hi, Uploaded 86efbad6d8677c64d057d92e1dd144988dee68f7a0faa84e5d12f1b59ded0e4f clang+llvm-9.0.0-rc4-armv7a-linux-gnueabihf.tar.xz eb37ced0868066fdf21a1539c61081b1b6e87f2fc6da58aa282230728329f80a clang+llvm-9.0.0-rc4-aarch64-linux-gnu.tar.xz Both seem fine. Cheers, Diana On Tue, 10 Sep 2019 at 12:26, Hans Wennborg via libcxx-dev wrote: > > Hello again, > > 9.0.0-rc4 was just tagged from the release_90 branch at r371490. In > the Git monorepo, it's tagged as llvmorg-9.0.0-rc4. > > Source code and docs are available at > https://prereleases.llvm.org/9.0.0/#rc4 Binaries will be added as they > become available. > > There are not a lot of changes from rc3 to rc4, and there are again no > open release blockers, so I'm hoping this will be the last release > candidate and that we can tag the final release soon. > > Please file bug reports for any issues you find, marking them blocking > of https://llvm.org/PR42474 > > Release testers, please run the test script, share your results, and > upload binaries. > > Thanks, > Hans > ___ > libcxx-dev mailing list > libcxx-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/libcxx-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [Release-testers] [9.0.0 Release] Release Candidate 3 is here
ARM & AArch64 uploaded: 655d6ed6f8038d3203aa446e7dad11f63eeb58625bce6b381e4a5e5cc90e9d4c clang+llvm-9.0.0-rc3-aarch64-linux-gnu.tar.xz ee9a69a75616a2d0fe60b04b78fcfdb04cf1668960d15ba064b7557e2ccf80f9 clang+llvm-9.0.0-rc3-armv7a-linux-gnueabihf.tar.xz No new hiccups. Cheers, Diana On Mon, 2 Sep 2019 at 17:38, Michał Górny via cfe-dev wrote: > > On Sun, 2019-09-01 at 16:21 +0200, Michał Górny via Release-testers > wrote: > > On Fri, 2019-08-30 at 18:38 +0200, Hans Wennborg via Release-testers > > wrote: > > > Hello everyone, > > > > > > 9.0.0-rc3 was tagged today from the release_90 branch at r370450. In > > > the Git monorepo, it's tagged as llvmorg-9.0.0-rc3. > > > > > > Source code and docs are available at > > > https://prereleases.llvm.org/9.0.0/#rc3 > > > > > > Binaries will be added as they become available. > > > > > > There are currently no open release blockers, which means if nothing > > > new comes up, the final release could ship soon and this is what it > > > would look like (except for more release notes, which are still very > > > welcome). > > > > > > > I'm sorry for noticing it this late (I was on vacation) but it seems > > that 9.x has some regression that causes the following tests to hang > > on NetBSD: > > > > LLVM :: ExecutionEngine/MCJIT/eh-lg-pic.ll > > LLVM :: ExecutionEngine/MCJIT/eh.ll > > LLVM :: ExecutionEngine/MCJIT/multi-module-eh-a.ll > > LLVM :: ExecutionEngine/OrcMCJIT/eh-lg-pic.ll > > LLVM :: ExecutionEngine/OrcMCJIT/eh.ll > > LLVM :: ExecutionEngine/OrcMCJIT/multi-module-eh-a.ll > > > > I've been able to pinpoint first bad commit as r364550: > > > > Bitcode: derive all types used from records instead of Values. > > > > However, it seems that trunk works fine. I'm currently searching > > for a possible fix, and I will request backporting once I find it. > > > > I've filed [1] for the backport. However, it seems that we need this > linking for reasons other than listed in the commit message. > > [1] https://bugs.llvm.org/show_bug.cgi?id=43196 > > -- > Best regards, > Michał Górny > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [cfe-dev] 8.0.1-final has been tagged
Hi, It's been brought to my attention that the AArch64 archive is corrupted (it ends unexpectedly when trying to untar). I have re-run the script and uploaded a new one: 0672ccf5b2f16e31994e41094aad890851d45fb69b58c4429aa0a7fde50e9510 clang+llvm-8.0.1-aarch64-linux-gnu.tar.xz Tom, could you please hook this up on the release page? Thanks and sorry about the trouble, Diana On Tue, 23 Jul 2019 at 10:12, Diana Picus wrote: > > ARM & AArch64 ready: > c87b57496f8ec0f0fd74faa1c43b0ac12c156aae54d9be45169fd8f2b33b2181 > clang+llvm-8.0.1-armv7a-linux-gnueabihf.tar.xz > a80dc5ca8d9bf5dfb12502263fd50bde6260fe661c1d1f6fb88c7a1146c879f4 > clang+llvm-8.0.1-aarch64-linux-gnu.tar.xz > > Cheers, > Diana > > On Mon, 22 Jul 2019 at 21:40, Hans Wennborg via Release-testers > wrote: > > > > On Fri, Jul 19, 2019 at 8:21 PM Tom Stellard via cfe-dev > > wrote: > > > > > > Hi, > > > > > > The 8.0.1 final release has been tagged. Testers please upload the final > > > binaries. > > > > Windows is ready: > > > > $ sha256sum *8.0.1-win*.exe > > 5d992a41f1ff6296659e66eabbcbaec34f5533fe9d1376fc94fba7450383fe69 > > LLVM-8.0.1-win32.exe > > e3af139c2f93075c13dcbc4091c1311f66fc6e4e8705649fcaf9bef8b3368f41 > > LLVM-8.0.1-win64.exe > > > > Thanks, > > Hans > > ___ > > Release-testers mailing list > > release-test...@lists.llvm.org > > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [9.0.0 Release] Release Candidate 1 is here
Uploaded ARM and AArch64: 1e091722ba37c983d0b1bc97374a43bfc097833d94377ad4e8ef2353d5bec315 clang+llvm-9.0.0-rc1-aarch64-linux-gnu.tar.xz e88a380e7498985fed572893a333408aba595b3efbf3a730cedb2ae4399a18a2 clang+llvm-9.0.0-rc1-armv7a-linux-gnueabihf.tar.xz Both suffer from PR42739 (difference between Phase 2 and Phase 3 files). Also opened PR42841 for AArch64 libfuzzer test failures. Cheers, Diana On Mon, 29 Jul 2019 at 16:32, Hans Wennborg via lldb-dev wrote: > > Hi everyone, > > 9.0.0-rc1 was just tagged from the release_90 branch at r367217 > (tagged as llvmorg-9.0.0-rc1 in the Git monorepo). > > Source code and docs are available at https://prereleases.llvm.org/9.0.0/#rc1 > > Binaries will be added as they become available. > > Please file bug reports for any issues you find as blockers of > https://llvm.org/PR42474 > > Release testers: please start your engines, run the script, share your > results, and upload binaries. > > Thanks, > Hans > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [cfe-dev] 8.0.1-final has been tagged
ARM & AArch64 ready: c87b57496f8ec0f0fd74faa1c43b0ac12c156aae54d9be45169fd8f2b33b2181 clang+llvm-8.0.1-armv7a-linux-gnueabihf.tar.xz a80dc5ca8d9bf5dfb12502263fd50bde6260fe661c1d1f6fb88c7a1146c879f4 clang+llvm-8.0.1-aarch64-linux-gnu.tar.xz Cheers, Diana On Mon, 22 Jul 2019 at 21:40, Hans Wennborg via Release-testers wrote: > > On Fri, Jul 19, 2019 at 8:21 PM Tom Stellard via cfe-dev > wrote: > > > > Hi, > > > > The 8.0.1 final release has been tagged. Testers please upload the final > > binaries. > > Windows is ready: > > $ sha256sum *8.0.1-win*.exe > 5d992a41f1ff6296659e66eabbcbaec34f5533fe9d1376fc94fba7450383fe69 > LLVM-8.0.1-win32.exe > e3af139c2f93075c13dcbc4091c1311f66fc6e4e8705649fcaf9bef8b3368f41 > LLVM-8.0.1-win64.exe > > Thanks, > Hans > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] 8.0.1-rc4 release has been tagged.
Hi, ARM & AArch64 seem fine: ef4f41dc77483754efee9a6e158f28725f22b29f7e4483a1ab1442b4b75dc7cd clang+llvm-8.0.1-rc4-aarch64-linux-gnu.tar.xz 39a47e3d1ecedad627153d618afb3d15675a498c67f2691c93382679e3788911 clang+llvm-8.0.1-rc4-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Thu, 11 Jul 2019 at 05:25, Tom Stellard via cfe-dev wrote: > > Hi, > > I've tagged the 8.0.1-rc4 release, please begin testing. This will > (hopefully) > be the last release candidate. If all goes well, I will tag the final release > next Wednesday. > > -Tom > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] LLVM 7.1.0-final has been tagged
ARM looks good too: bac0c55c1943ee4e4eece850e18cc9cbd638e5c84f397b8897c0a8486f73431b clang+llvm-7.1.0-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Mon, 15 Apr 2019 at 10:33, Diana Picus wrote: > > AArch64 looks good: > b7369d91279cfc470f82528c23318b902adea8e345b7d64a59332c7f6900acfe > clang+llvm-7.1.0-aarch64-linux-gnu.tar.xz > > ARM coming up later. > > Cheers, > Diana > > On Fri, 12 Apr 2019 at 02:00, Tom Stellard via Release-testers > wrote: > > > > Hi, > > > > I've just tagged LLVM 7.1.0-final. Testers, please upload the final > > binaries. > > > > Thanks, > > Tom > > ___ > > Release-testers mailing list > > release-test...@lists.llvm.org > > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] LLVM 7.1.0-final has been tagged
AArch64 looks good: b7369d91279cfc470f82528c23318b902adea8e345b7d64a59332c7f6900acfe clang+llvm-7.1.0-aarch64-linux-gnu.tar.xz ARM coming up later. Cheers, Diana On Fri, 12 Apr 2019 at 02:00, Tom Stellard via Release-testers wrote: > > Hi, > > I've just tagged LLVM 7.1.0-final. Testers, please upload the final binaries. > > Thanks, > Tom > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [Release-testers] Release 7.1.0 -rc1 has been tagged
ARM & AArch64 all green: fa208f1d15ae8d4babc93cd421af6d23868f8bb6a16f64fa89f18920c133d982 clang+llvm-7.1.0-rc1-aarch64-linux-gnu.tar.xz 760a06933b45cffcf7340c15e1a04a4dce122677c9132291a9da4d64dd84edca clang+llvm-7.1.0-rc1-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Fri, 29 Mar 2019 at 17:51, Dimitry Andric via cfe-dev wrote: > > On 27 Mar 2019, at 22:27, Tom Stellard via Release-testers > wrote: > > > > I've just tagged 7.1.0-rc1. Testers, please begin testing and reporting > > results. > > Main test results on amd64-freebsd11: > > Expected Passes: 52441 > Expected Failures : 232 > Unsupported Tests : 3687 > Unexpected Passes : 1 > Unexpected Failures: 495 > > Test suite results on amd64-freebsd11: > > Expected Passes: 903 > Unexpected Failures: 3 > > Main test results on i386-freebsd11: > > Expected Passes: 50252 > Expected Failures : 226 > Unsupported Tests : 2502 > Unexpected Failures: 276 > > As before, the test suite fails to compile on i386, due to an SSE requirement. > > Uploaded: > > SHA256 (clang+llvm-7.1.0-rc1-amd64-unknown-freebsd11.tar.xz) = > f607f8b33838ba31684da09f7956d273e60dbd99e5d4a2066315efccb52556bb > SHA256 (clang+llvm-7.1.0-rc1-i386-unknown-freebsd11.tar.xz) = > 221c31b8dc19965271e47b422c30175fa70446a05fbb6f4dff9ba3f8020e8437 > > -Dimitry > > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [8.0.0 Release] The final tag is in
Uploaded ARM & AArch64: 998e9ae6e89bd3f029ed031ad9355c8b43441302c0e17603cf1de8ee9939e5c9 clang+llvm-8.0.0-aarch64-linux-gnu.tar.xz ddcdc9df5c33b77740e4c27486905c44ecc3c4ec178094febeab60124deb0cc2 clang+llvm-8.0.0-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Wed, 20 Mar 2019 at 14:39, Brian Cain via Release-testers wrote: > > Uploaded ubuntu and SLES tarballs: > > db0a5f7729507ddc4b161eff70cffcf5de052347 > clang+llvm-8.0.0-x86_64-linux-sles11.3.tar.xz > 2be69be355b012ae206dbc0ea7d84b831d77dc27 > clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz > 6aeb8aa0998d37be67d886b878f27de5e5ccc5e4 > clang+llvm-8.0.0-x86_64-linux-gnu-ubuntu-18.04.tar.xz > > > On Mon, Mar 18, 2019 at 8:04 AM Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> The final version of 8.0.0 was just tagged from the release_80 branch >> at r356364. It's identical to rc5 except for a few documentation >> changes. >> >> Apologies for being behind schedule. It took longer than planned this time. >> >> Please build the final binaries and upload to the sftp. >> >> For those following along: this means 8.0.0 is done, but it will take >> a few days to get all the tarballs ready and published on the release >> web page. I will send the announcement once everything is ready. >> >> Thanks again everyone for your help with testing the release! >> >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > > -- > -Brian > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [Release-testers] [8.0.0 Release] rc5 has been tagged
Hi, Uploaded ARM and AArch64: 251162b7f91dfc05e569e6a8a035e8a4ada94c2faa4bf6ffabb73795ab865fab clang+llvm-8.0.0-rc5-aarch64-linux-gnu.tar.xz 18f37388546d5579423eaa1d08a77e8b8a426d2d053edb125569fddde980f796 clang+llvm-8.0.0-rc5-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Fri, 15 Mar 2019 at 21:32, Brian Cain via cfe-dev wrote: > > Hans, > > Sorry for the delay -- uploaded rc5 binaries: > > d52493c1c1082ae6be0a322a1b2d4a81e9f0d6c7 > clang+llvm-8.0.0-rc5-x86_64-linux-gnu-ubuntu-18.04.tar.xz > af43eb9c4394175d26ff795d35dea2a5b4db80fa > clang+llvm-8.0.0-rc5-x86_64-linux-gnu-ubuntu-14.04.tar.xz > 635cb99931ac9b166fa60702ac05b8e3a09a0290 > clang+llvm-8.0.0-rc5-x86_64-linux-sles11.3.tar.xz > > > > On Tue, Mar 12, 2019 at 6:17 AM Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> 8.0.0-rc5 was just tagged from the release_80 branch at r355909. >> >> This is identical to rc4 with the addition of r355743. Hopefully it is the >> final release candidate, so please give it a good testing. >> >> As usual, please run the test script, share your results, and upload >> binaries. >> >> I'll publish source tarballs and docs as soon as possible, and binaries as >> they become available. >> >> Thanks for all your help so far, we're almost there :-) >> >> Cheers, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > > -- > -Brian > ___ > cfe-dev mailing list > cfe-...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [8.0.0 Release] rc2 has been tagged
Uploaded ARM & AArch64:
9432315fe814e5edc667467bc1b3ce4817084edc
clang+llvm-8.0.0-rc2-aarch64-linux-gnu.tar.xz
fb7f587de673837c82da47209ec9d9ed72f9b27f
clang+llvm-8.0.0-rc2-armv7a-linux-gnueabihf.tar.xz
Same as before, ARM looks fine but we have a MSan failure on AArch64
(I haven't yet managed to reproduce it outside Jenkins though, I'll
try harder).
Cheers,
Diana
On Mon, 11 Feb 2019 at 17:34, Paweł Sikora via cfe-dev
wrote:
>
>
>
>
> On Fri, Feb 8, 2019 at 9:53 AM Paweł Sikora via cfe-dev
> wrote:
>>
>> - Oryginalna wiadomość -
>> > Dear testers,
>> >
>> > 8.0.0-rc2 has been tagged from the release_80 branch at r353413.
>>
>> Hi,
>> i've noticed a compile error with rc2 and libc++ (release_80 @svn). looks
>> similar to https://bugs.llvm.org/show_bug.cgi?id=40559
>> (...)
>> (...)/sysroot-x86_64-linux-gnu/usr/include/c++/v1/type_traits:740:56: error:
>> _Float16 is not supported on this target
>> template <> struct __libcpp_is_floating_point<_Float16>: public
>> true_type {};
>
>
> This is quite odd, because libc++ trunk has no mentions of `_Float16`, and I
> see none here:
>
> https://llvm.org/svn/llvm-project/libcxx/branches/release_80/include/type_traits
>
> oh, my fault, these headers were from release_70 branch. the 8.0rc2 works
> fine, sorry for the noise.
>
> regards,
> pawel.
>
> ___
> cfe-dev mailing list
> cfe-...@lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc1 has been tagged
ARM looks good. Uploaded. 358fc71b8021eddbb1b93142bc09f1ad698677a6 clang+llvm-8.0.0-rc1-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On Wed, 30 Jan 2019 at 05:45, Brian Cain via Release-testers wrote: > > > SLES and Ubuntu 14.04 tarballs uploaded. Sorry for the delay. I will try > and find time to make a build for bionic / 18.04 too. > > 99ec00702e39b096ace4fbce3d787b9e485b879e > clang+llvm-8.0.0-rc1-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > dbf204f70cb09ec459e5eb4fc14e8fa71292daa7 > clang+llvm-8.0.0-rc1-x86_64-linux-sles11.3.tar.xz > > > On Wed, Jan 23, 2019 at 6:50 PM Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> 8.0.0-rc1 was just tagged (from the branch at r351980). >> >> It took a little longer than planned, but it's looking good. >> >> Please run the test script, share your results, and upload binaries. >> >> I'll get the source tarballs and docs published as soon as possible, >> and binaries as they become available. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > > -- > -Brian > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [8.0.0 Release] rc1 has been tagged
Uploaded AArch64 binaries: 2c3bd3d686c3712ba5699e9a638bc849ddb0aae3 clang+llvm-8.0.0-rc1-aarch64-linux-gnu.tar.xz Had one failure in check-all (memory sanitizer). I opened PR40511 for it [1]. I ran into some snags with ARM, I'm still figuring out if there's something wrong with our infrastructure. Sorry about the delay! Cheers, Diana [1] https://bugs.llvm.org/show_bug.cgi?id=40511 On Tue, 29 Jan 2019 at 00:23, Bero Rosenkränzer via Release-testers wrote: > > Hi, > working without immediately obvious regressions on OpenMandriva x86-64, x86, > aarch64 and armv7hnl. > Since our 4.0 release is imminent, 8.0 won't go in there, but it will be our > main compiler the day after the release and been cut. > > Would be nice to get the admin goto patches in to enable building the Linux > kernel, but unfortunately that may be too big a change after RC? > > ttyl > bero > > On Thu, Jan 24, 2019, 3:50 AM Hans Wennborg via Release-testers > > >> Dear testers, >> >> 8.0.0-rc1 was just tagged (from the branch at r351980). >> >> It took a little longer than planned, but it's looking good. >> >> Please run the test script, share your results, and upload binaries. >> >> I'll get the source tarballs and docs published as soon as possible, >> and binaries as they become available. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [cfe-dev] [Openmp-dev] [6.0.0 Release] The final tag is in
Hi, ARM & AArch64 also up and ready: fb00698f38ade92d11d1aa297daf4c6ea657560a clang+llvm-6.0.0-aarch64-linux-gnu.tar.xz c4fd61dd28a90b754d0d39f3f1f2bffcd5b38e46 clang+llvm-6.0.0-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On 7 March 2018 at 19:15, Simon Dardis via cfe-dev wrote: > Hi Hans, > > Looks ok here. I've uploaded the binaries. > > SHA256(clang+llvm-6.0.0-mipsel-linux-gnu.tar.xz)= > 5ff062f4838ac51a3500383faeb0731440f1c4473bf892258314a49cbaa66e61 > SHA256(clang+llvm-6.0.0-mips-linux-gnu.tar.xz)= > 39820007ef6b2e3a4d05ec15feb477ce6e4e6e90180d00326e6ab9982ed8fe82 > SHA256(clang+llvm-6.0.0-x86_64-linux-gnu-debian8.tar.xz)= > ff55cd0bdd0b67e22d1feee2e4c84dedc3bb053401330b64c7f6ac18e88a71f1 > > > Thanks, > Simon > > From: Openmp-dev [openmp-dev-boun...@lists.llvm.org] on behalf of Hans > Wennborg via Openmp-dev [openmp-...@lists.llvm.org] > Sent: Friday, March 2, 2018 12:17 PM > To: Release-testers > Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev > Subject: [Openmp-dev] [6.0.0 Release] The final tag is in > > Dear testers, > > The final version of 6.0.0 has just been tagged from the branch after > r326550. It has the same contents as -rc3 modulo release notes and one > small x86 fix (r326393). > > Please build the final binaries and upload to the sftp. > > For those following along: this means llvm-6.0.0 is complete, but it > will take a few days to get all the tarballs ready and published on > the web page. I will send the announcement once everything is ready. > > Many thanks to everyone for your hard work! > > Hans > ___ > Openmp-dev mailing list > openmp-...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/openmp-dev > ___ > 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] [Release-testers] [6.0.0 Release] Release Candidate 3 tagged
ARM & AArch64 uploaded: 4b941502895a501b96da4dfc1ae97daf76b1dce0 clang+llvm-6.0.0-rc3-aarch64-linux-gnu.tar.xz 66e2e7142f3b6ce3e2d02aea5b64d6ada9e6f6a5 clang+llvm-6.0.0-rc3-armv7a-linux-gnueabihf.tar.xz AArch64 is green, but for ARM we still have PR34182 (as expected). No new failures though. Cheers, Diana On 24 February 2018 at 06:43, Brian Cain via cfe-dev wrote: > SLES11 binaries for rc3 uploaded. > > 55b63de8adc12c67eb11abcf1a5f7132cca59b4e > clang+llvm-6.0.0-rc3-x86_64-linux-sles11.3.tar.xz > > > On Fri, Feb 23, 2018 at 9:14 AM, Hans Wennborg via Release-testers > wrote: >> >> Dear testers, >> >> 6.0.0-rc3 was just tagged, after r325901 on the branch. >> >> There are still a few open blockers, but I'm not sure we'll actually >> end up blocking on all of them. So depending on what comes up, this >> release candidate is probably pretty close to what the final release >> will look like (I'm still hoping for more release notes, though). >> >> I'm hoping we can get to 'final' sometime next week. >> >> Please test, let me know how it goes, and upload binaries. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > > > -- > -Brian > > ___ > 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] [Release-testers] [6.0.0 Release] Release Candidate 2 tagged
Uploaded ARM & AArch64: 929794f931a075b9981ac0b3828b74ff0a78c541 clang+llvm-6.0.0-rc2-aarch64-linux-gnu.tar.xz e1bebfc9c6dbbbdac3be0d629850442a0418b242 clang+llvm-6.0.0-rc2-armv7a-linux-gnueabihf.tar.xz The good news is that the previous issues have been fixed, the bad news is there are two new ones: PR36313 on AArch64 (failures in openmp tests) PR34182 on ARM (libcxxabi, we've seen this before in 5.0.0 but it was reverted on the release branch; I'm really sorry that I missed this in rc1, it got lost among all the tautological compare failures) Cheers, Diana On 8 February 2018 at 22:43, Dimitry Andric via Release-testers wrote: > On 7 Feb 2018, at 21:51, Hans Wennborg via Release-testers > wrote: >> >> There's been a lot of merges since rc1, and hopefully the tests are in >> a better state now. >> >> 6.0.0-rc2 was just tagged, after r324506. >> >> Please test, let me know how it goes, and upload binaries. > > Built, tested and uploaded: > > SHA256 (clang+llvm-6.0.0-rc2-amd64-unknown-freebsd10.tar.xz) = > 1334db5949ec0c78cd6e9b798f0b397fe9e99240d98bcfc834e4410258b98372 > SHA256 (clang+llvm-6.0.0-rc2-i386-unknown-freebsd10.tar.xz) = > a7c0b1e4cfe3d608ee77472c7f17fe6b9493c7259aca80fcdd3b8a4fe49ad92d > > On amd64-freebsd10 there were 896 unexpected test failures: > > Expected Passes: 45004 > Expected Failures : 186 > Unsupported Tests : 2939 > Unexpected Failures: 896 > > On i386-freebsd10 there were 619 unexpected test failures: > > Expected Passes: 43849 > Expected Failures : 195 > Unsupported Tests : 1954 > Unexpected Failures: 619 > > At least the i386 version looks quite a bit better, down from 1773 to 619 > test failures. :) > > -Dimitry > > > ___ > 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] [6.0.0 Release] Release Candidate 1 tagged
Hi, Uploaded ARM & AArch64: b84b25397a4ea479d08c056b20582fd0a8e16bb6 clang+llvm-6.0.0-rc1-aarch64-linux-gnu.tar.xz c19100cf7fb1d0fea80ed3e761bfd293e807b59a clang+llvm-6.0.0-rc1-armv7a-linux-gnueabihf.tar.xz I am seeing some failures in compiler-rt (ARM, AArch64) and libcxx (just ARM), for which I have filed PR35996 and PR35997. Cheers, Diana On 18 January 2018 at 04:17, Bero Rosenkränzer via Release-testers wrote: > We're now using it as the main compiler in the OpenMandriva > development builds -- no issues so far (after rebuilding a couple of > key packages for testing). > > ttyl > bero > > On 17 January 2018 at 18:53, Hans Wennborg via Release-testers > wrote: >> Dear testers, >> >> Start your engines; 6.0.0-rc1 was just tagged. >> >> I know there are still open blockers and it's early in the process in >> a way, but I'd like to find out where we are. Please run the test >> script, let me know the results, and upload binaries. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > ___ > 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] [5.0.0 Release] The final tag is in
Hi, Uploaded ARM and AArch64: ad5a072fc558c740992829bdb4e5d868634f1bec clang+llvm-5.0.0-aarch64-linux-gnu.tar.xz f5cba70b09845bcb50d47a4d1aff4c2b20c0edc6 clang+llvm-5.0.0-armv7a-linux-gnueabihf.tar.xz No new failures. Cheers, Diana On 6 September 2017 at 12:38, Dimitry Andric via Release-testers wrote: > On 5 Sep 2017, at 20:24, Hans Wennborg via Release-testers > wrote: >> >> The final version of 5.0.0 has just been tagged. There were no changes >> after rc5. > > Built and tested on FreeBSD 10, and uploaded: > > SHA256 (clang+llvm-5.0.0-amd64-unknown-freebsd10.tar.xz) = > e55b646390da0a24e27f9761eecf0b31936483c9a3e84c12de0bb1a0d95bab6c > SHA256 (clang+llvm-5.0.0-i386-unknown-freebsd10.tar.xz) = > 2ea32ad7cd30d8e849113747b5bfda8e6eb0fb2f9b01cbe9eb61e884c0bd69eb > > -Dimitry > > > ___ > 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] [5.0.0 Release] Release Candidate 5 tagged
Hi, No new failures on ARM and AArch64. Uploaded: 6a2ea497ba48682b8bfd255a7e6dd668678ff6c0 clang+llvm-5.0.0-rc5-aarch64-linux-gnu.tar.xz ac44320509a6e15f948bb6ca11a85faa5e24be30 clang+llvm-5.0.0-rc5-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On 2 September 2017 at 21:52, Dimitry Andric via Release-testers wrote: > On 1 Sep 2017, at 23:07, Hans Wennborg via Release-testers > wrote: >> >> 5.0.0-rc5 was just tagged. >> >> I had hoped rc4 would be the last one, but I think we needed the fix >> for PR34381. > > Built and tested on FreeBSD 10, no changes with respect to the previous rc. > I've uploaded: > > SHA256 (clang+llvm-5.0.0-rc5-amd64-unknown-freebsd10.tar.xz) = > c10eae93c15ce3f00405fcf9e1c596f91b8f4c1f64b65b426648b07b1e842e9e > SHA256 (clang+llvm-5.0.0-rc5-i386-unknown-freebsd10.tar.xz) = > 0b7f2e18aa1c07b72581dd23fbe3945a4c756f3ee224cd9e3c2dcc56227654dd > > -Dimitry > > > ___ > 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] [llvm-dev] [5.0.0 Release] Release Candidate 4 tagged
Hi, ARM and AArch64 uploaded: 64414576baf177aa3de789343399bf662292 clang+llvm-5.0.0-rc4-aarch64-linux-gnu.tar.xz d8a55e393f6277759165ad89d5b0f1b5a540c81b clang+llvm-5.0.0-rc4-armv7a-linux-gnueabihf.tar.xz No new failures. Cheers, Diana On 30 August 2017 at 08:24, Somchai Smythe via llvm-dev wrote: > Download link? > > On 8/30/17, Hans Wennborg via llvm-dev wrote: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what the final release will look like. >> >> Please test and let me know if there are any issues. >> >> Cheers, >> Hans >> ___ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > ___ > 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] [Release-testers] [llvm-dev] [5.0.0 Release] Release Candidate 3 tagged
Hi, Uploaded ARM & AArch64: ee9e89f1d5f8a5fb84cef6c82ded694c5c427e16 clang+llvm-5.0.0-rc3-aarch64-linux-gnu.tar.xz a8b38e91288b07b2899c397373c018c6c5f6f207 clang+llvm-5.0.0-rc3-armv7a-linux-gnueabihf.tar.xz The libunwind tests are still failing. I have reopened the bug: https://bugs.llvm.org/show_bug.cgi?id=33858 Cheers, Diana On 28 August 2017 at 09:46, Sylvestre Ledru via Release-testers wrote: > Hello > > I am not sure to understand how this relates to the 5.0.0 work? > > For now, it is broken because of a gcc bug: > > https://bugs.llvm.org/show_bug.cgi?id=34150 > > I am planning to upgrade the gcc version to 4.9 to workaround this issue. > Probably this week. > > Sylvestre > > > Le 28/08/2017 à 09:40, Andrew Kelley via Release-testers a écrit : > > trusty on apt.llvm.org is behind the others by 9 days and is missing the > latest rc3 release. Can we get an update on this? > > Regards, > Andrew > > On Fri, Aug 25, 2017 at 6:52 PM, Hans Wennborg via llvm-dev > wrote: >> >> Dear testers, >> >> 5.0.0-rc3 was just tagged. >> >> This is a release candidate in the real sense: if nothing bad comes up >> in testing, this is what the release is going to look like. >> >> Please build, test and upload binaries to the sftp (use the >> /data/testers-uploads/ directory) and let me know what issues remain. >> >> I know we're a little bit behind schedule, but hopefully we can get to >> 'final' soon. >> >> Cheers, >> Hans >> ___ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > > ___ > 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] [cfe-dev] [llvm-dev] [Release-testers] [5.0.0 Release] Release Candidate 2 tagged
Hi, Uploaded ARM and AArch64: b0a84bc679946b733803b8a687e4f0fb84d2f643 clang+llvm-5.0.0-rc2-aarch64-linux-gnu.tar.xz d5a275f470687beaf2aabc279926c4430da1c88e clang+llvm-5.0.0-rc2-armv7a-linux-gnueabihf.tar.xz AArch64 has the same failures as before (PR33858, libunwind tests, and PR33972, allocator_oom_test). ARM has the same failures as before (PR33858, libunwind tests) and also a new one in libcxxabi, which I've reported as PR34182. Cheers, Diana On 12 August 2017 at 07:37, Brian Cain via cfe-dev wrote: > Opened https://bugs.llvm.org/show_bug.cgi?id=34168 > > rc2 uploaded to > /home/testers/uploads/clang+llvm-5.0.0-rc2-linux-x86_64-sles11.3.tar.xz -- I > tried to use /data/testers-uploads/ but that failed. > > 292e39fe52d7404fcd5cd962cf8917600d45f507 > rc2/clang+llvm-5.0.0-rc2-linux-x86_64-sles11.3.tar.xz > > > On Fri, Aug 11, 2017 at 7:36 PM, Matthias Braun wrote: >> >> +CC Alina >> >> Maybe the bitcode is generated too aggressively and we should find ways to >> disable the Bitcode tests if the host CPU isn't new enough (or alternatively >> disable the bitcode tests by default and only enable them when someone asks >> for them via TEST_SUITE_SUBDIRS?) >> >> - Matthias >> >> > On Aug 11, 2017, at 4:44 PM, Hans Wennborg via llvm-dev >> > wrote: >> > >> > I'm not aware of a bug filed for this, so please file one. I don't >> > know much about the workings of test-suite myself, though. >> > >> > On Fri, Aug 11, 2017 at 2:54 PM, Brian Cain >> > wrote: >> >> Much or all of "Bitcode/simd_ops/simd_ops_*.test" (254 failures) seem >> >> to be >> >> failing for me with SIGILL. I'm guessing that my host CPU doesn't >> >> support >> >> the instructions we're testing? >> >> >> >> Is there already a bug on this failure? Are there any CPUID-style >> >> feature >> >> detection flags I can easily add to mark these tests UNSUPPORTED for, >> >> or >> >> would I have to write this detection feature? >> >> >> >> On Thu, Aug 10, 2017 at 9:00 PM, Hans Wennborg via Release-testers >> >> wrote: >> >>> >> >>> Dear testers, >> >>> >> >>> 5.0.0-rc2 was just tagged. >> >>> >> >>> I know we still have a bunch of open release blockers, but there has >> >>> been a lot of merged patches and I'd like to find out what the status >> >>> is. >> >>> >> >>> Please build, test and upload binaries to the sftp. When uploading, >> >>> make sure to use the /data/testers-uploads/ directory on the server. >> >>> Let me know if there are any issues. >> >>> >> >>> I'll upload sources, docs and your binaries to the pre-release website >> >>> once they're ready. >> >>> >> >>> Cheers, >> >>> Hans >> >>> ___ >> >>> Release-testers mailing list >> >>> release-test...@lists.llvm.org >> >>> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers >> >> >> >> >> >> >> >> >> >> -- >> >> -Brian >> > ___ >> > LLVM Developers mailing list >> > llvm-...@lists.llvm.org >> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > > > > -- > -Brian > > ___ > 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] [Release-testers] [5.0.0 Release] Release Candidate 1 tagged
Hi, ARM and AArch64 ready. Both fail in libunwind_01.pass.cpp and libunwind_02.pass.cpp (PR33858). In addition, ARM has a failure in libunwind's alignment.pass.cpp (also PR33858), and AArch64 has one in the sanitizers, allocator_oom_test (PR33972). sha1sums: 3e83e4f5f249a0f3974c37070051cd29fafc0614 clang+llvm-5.0.0-rc1-aarch64-linux-gnu.tar.xz 2f5baefae0b84b314c1f71e865fbd3093184e800 clang+llvm-5.0.0-rc1-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On 28 July 2017 at 08:43, Sylvestre Ledru via Release-testers wrote: > Hello, > > I am experiencing a build issue with clang tools extra that I reported here: > > https://bugs.llvm.org/show_bug.cgi?id=33970 > > Does it ring a bell? > > Thanks > > S > > > > Le 27/07/2017 à 00:41, Hans Wennborg via Release-testers a écrit : >> Dear testers, >> >> 5.0.0-rc1 has just been tagged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. >> >> I'll upload sources, docs, and your binaries to the pre-release >> website once they're ready. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > ___ > 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] LLVM social in Sweden?
Hi everyone, We have started a meetup page for LLVM socials in Sweden [1]. Thanks to those that have already joined! We're going to keep most of the communication there from now on. Hopefully towards the end of next week I'll post another Doodle for scheduling the next event, which will take place somewhere in Stockholm [2]. We'd like to have some talks this time around, so if you're interested in giving one please let us know, either on the meetup page or by email. It can be as formal or informal as you want, and lightning talks are also welcome. Note that it doesn't have to be about your work, it can also be a tutorial, or a presentation of a problem that you've encountered while working with LLVM, or generally anything that you'd like to share with other LLVM devs/users. Even if you don't want to give a talk, you can feel free to suggest topics that are interesting to you, and maybe someone else will pick them up, or we can have some free-form discussions about them. See you around, Diana PS: Sorry about cross-posting, just getting the word out. [1] https://www.meetup.com/LLVM-Clang-Sweden-socials/ [2] If you're from another area, please feel free to start a discussion on meetup and we'll see if we can manage to get a few of us there. On 13 March 2017 at 10:00, Roberto Castañeda Lozano wrote: > Hi all, > > You can find how to get to SICS Kista here: > https://www.sics.se/contact/sics-stockholm . We are located at level 6, > elevator B. Just mention at the reception that you are attending the LLVM > social event held in the "Knuth" meeting room. > > See you on Wed! > > Roberto > > > On 2017-03-06 14:41, Diana Picus via llvm-dev wrote: >> >> Hi all, >> >> Based on the answers in the poll, it looks like a good time to hold >> the social is on Wednesday, March 15th, around 12 o'clock. Sorry to >> those that can't make it. >> >> SICS have offered to host us at their office in Kista [1]. Roberto >> (CC'ed) can give us more details on how to find the meeting room >> (which is booked until 5 PM, so don't worry if you're going to be a >> bit late). They are also providing pizzas and (non-alcoholic) drinks, >> so please let us know if you have any preferences / special requests >> regarding that. >> >> Thanks again to SICS! >> >> See you there, >> Diana >> >> [1] https://www.sics.se/contact/sics-stockholm >> >> On 27 February 2017 at 11:22, Diana Picus wrote: >>> >>> Hi all, >>> >>> Thanks for the answers! I've also received a couple of answers >>> off-list, so there should be enough of us to get something rolling. >>> >>> I think we should start with something informal to get to know each >>> other and see what our interests are etc. So, I've created a poll with >>> a random slice of March here [1], so we can sync on the date / time. >>> Please pick as many options as you can. The times are just ballpark >>> estimates, I'm trying to cover different scenarios in case people have >>> to take trains or have other constraints. Just pick whatever's closer >>> to what you prefer, and we'll settle on something more specific later >>> on. If you can't make it, please say so and we can try to do this in >>> April instead, so we can have more time to plan. >>> >>> I'm thinking of leaving this up for a week or so before deciding >>> something, but if you need to know sooner please say so. >>> >>> Also, any suggestions for venues are appreciated! >>> >>> Thanks, >>> Diana >>> >>> [1] http://doodle.com/poll/cfp7i7x98ad82h88 >>> >>> On 23 February 2017 at 11:58, Roberto Castañeda Lozano >>> wrote: On 2017-02-17 13:26, Diana Picus via llvm-dev wrote: > > > Hey, > > Anyone interested in organizing a meetup in Sweden? I'm based in > Stockholm, but I don't mind traveling around on a weekend if people > prefer to gather elsewhere. > > Cheers, > Diana > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev Hi Diana, I and probably some others from SICS (Swedish Institute of Computer Science) would be interested, we are based in Kista. Cheers, Roberto -- Roberto Castañeda Lozano Researcher @ SICS, PhD student @ KTH www.sics.se/~rcas >> >> ___ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > > > -- > Roberto Castañeda Lozano > Researcher @ SICS, PhD student @ KTH > www.sics.se/~rcas ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [4.0.0 Release] Release Candidate 2 has been tagged
Hi, AArch64 good to go. f27db27da7f75a435d89ba63c8a762885fd86a1a clang+llvm-4.0.0-rc2-aarch64-linux-gnu.tar.xz Diana On 9 February 2017 at 01:33, Hans Wennborg via Release-testers wrote: > Hello testers, > > 4.0.0-rc2 was just tagged from the branch at r294535. > > There are still open relase blocking bugs and merge requests, so this > will not be the last release candidate, but we've had a lot of merges > since the last one, and I'd like to see what the testing looks like. > > The test-release.sh script was updated to also include lld. Make sure > you're using the latest version of the script (ideally from the > branch, but the trunk version is identical), and if lld causes any > problems, pass the "-no-lld" flag. > > Please build, test, and upload binaries to the sftp. Let me know what > comes up, and I'll publish your binaries plus source and docs when > they're ready. > > Thanks, > Hans > ___ > 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] [cfe-dev] [4.0.0 Release] Relase Candidate 1 has been tagged
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 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-...@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] [Release-testers] [llvm-dev] [3.9 Release] Release Candidate 1 has been tagged
We're having some failures on AArch64, filed https://llvm.org/bugs/show_bug.cgi?id=28797 and investigating. Diana On 1 August 2016 at 10:18, Michael Kuperstein via Release-testers wrote: > The crash dump looks like it's probably PR27071. > The bug was introduced in r261387 (which was merged into 3.8) and fixed in > r264465 (which apparently wasn't). > > On Sun, Jul 31, 2016 at 3:50 PM, Bernhard Rosenkränzer > wrote: >> >> Hi, >> On the OpenMandriva side, x86_64 passes all checks. We're having some >> problems with other architectures though (see below): >> >> x86_64 succeeded, packages are here: >> https://abf.openmandriva.org/build_lists/76792 >> >> i586 fails to build, but this seems to be an issue with 3.8.1 (which we're >> using to build 3.9): >> >> /usr/bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS >> -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support >> -Iinclude -I../include -Os -pipe -Wformat -Werror=format-security >> -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 >> -fomit-frame-pointer -mtune=atom -march=i586 -fasynchronous-unwind-tables >> -march=i686 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 >> -D_FILE_OFFSET_BITS=64 -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-dtor -Wdelete-non-virtual-dtor >> -Werror=date-time -std=c++1y -fcolor-diagnostics -ffunction-sections >> -fdata-sections -Os -pipe -Wformat -Werror=format-security >> -D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 >> -fomit-frame-pointer -mtune=atom -march=i586 -fasynchronous-unwind-tables >> -march=i686 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 >> -D_FILE_OFFSET_BITS=64 -MD -MT >> lib/Support/CMakeFiles/LLVMSupport.dir/PrettyStackTrace.cpp.o -MF >> lib/Support/CMakeFiles/LLVMSupport.dir/PrettyStackTrace.cpp.o.d -o >> lib/Support/CMakeFiles/LLVMSupport.dir/PrettyStackTrace.cpp.o -c >> ../lib/Support/PrettyStackTrace.cpp >> clang-3.8: ../include/llvm/CodeGen/MachineOperand.h:411: int64_t >> llvm::MachineOperand::getImm() const: Assertion `isImm() && "Wrong >> MachineOperand accessor"' failed. >> #0 0xf4abd075 llvm::sys::PrintStackTrace(llvm::raw_ostream&) >> (/usr/lib/libLLVMSupport.so.3.8+0x95075) >> #1 0xf4abd2c7 (/usr/lib/libLLVMSupport.so.3.8+0x952c7) >> #2 0xf4abbbf1 llvm::sys::RunSignalHandlers() >> (/usr/lib/libLLVMSupport.so.3.8+0x93bf1) >> #3 0xf4abbf49 (/usr/lib/libLLVMSupport.so.3.8+0x93f49) >> #4 0xf7714d20 0xd20 __GI_raise >> #5 0xf7714d20 >> #6 0xf7714d20 __GI_abort (+0xd20) >> #7 0xf4650ef0 __GI___assert_fail (/lib/libc.so.6+0x26ef0) >> #8 0xf46520e5 __GI___assert_perror_fail (/lib/libc.so.6+0x280e5) >> #9 0xf464b126 (/lib/libc.so.6+0x21126) >> #10 0xf464b162 llvm::X86InstrInfo::getSPAdjust(llvm::MachineInstr >> const*) const (/lib/libc.so.6+0x21162) >> #11 0xf65a0db6 (/usr/lib/libLLVMX86CodeGen.so.3.8+0x30db6) >> #12 0xf667640d (/usr/lib/libLLVMX86CodeGen.so.3.8+0x10640d) >> #13 0xf61029dc >> llvm::MachineFunctionPass::runOnFunction(llvm::Function&) >> (/usr/lib/libLLVMCodeGen.so.3.8+0x1739dc) >> #14 0xf6105002 llvm::FPPassManager::runOnFunction(llvm::Function&) >> (/usr/lib/libLLVMCodeGen.so.3.8+0x176002) >> #15 0xf60ab337 llvm::FPPassManager::runOnModule(llvm::Module&) >> (/usr/lib/libLLVMCodeGen.so.3.8+0x11c337) >> #16 0xf50d7e6f llvm::legacy::PassManagerImpl::run(llvm::Module&) >> (/usr/lib/libLLVMCore.so.3.8+0x19de6f) >> #17 0xf50d816b llvm::legacy::PassManager::run(llvm::Module&) >> (/usr/lib/libLLVMCore.so.3.8+0x19e16b) >> #18 0xf50d857f clang::EmitBackendOutput(clang::DiagnosticsEngine&, >> clang::CodeGenOptions const&, clang::TargetOptions const&, >> clang::LangOptions const&, llvm::StringRef, llvm::Module*, >> clang::BackendAction, llvm::raw_pwrite_stream*) >> (/usr/lib/libLLVMCore.so.3.8+0x19e57f) >> #19 0xf50d8734 (/usr/lib/libLLVMCore.so.3.8+0x19e734) >> #20 0xf59fc72c clang::ParseAST(clang::Sema&, bool, bool) >> (/usr/lib/libclangCodeGen.so.3.8+0x6972c) >> #21 0xf5b2cd85 clang::ASTFrontendAction::ExecuteAction() >> (/usr/lib/libclangCodeGen.so.3.8+0x199d85) >> #22 0xf3b2b294 clang::CodeGenAction::ExecuteAction() >> (/usr/lib/libclangParse.so.3.8+0x24294) >> #23 0xf582583e clang::FrontendAction::Execute() >> (/usr/lib/libclangFrontend.so.3.8+0x8783e) >> #24 0xf5b2d3e1 >> clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) >> (/usr/lib/libclangCodeGen.so.3.8+0x19a3e1) >> #25 0xf5826660 >> clang::ExecuteCompilerInvocation(clang::CompilerInstance*) >> (/usr/lib/libclangFrontend.so.3.8+0x88660) >> #26 0xf58029e1 cc1_main(llvm::ArrayRef, char const*, >> void*) (/usr/lib/libclangFrontend.so.3.8+0x649e1) >> #27 0xf579aead main (/usr/lib/libclangFrontendTool.
Re: [lldb-dev] [cfe-dev] Switching to git (Windows experience) (was re: GitHub anyone?)
You could try Git GUI [1]. I don't know if it's any good, I've only used Git BASH on Windows (never had any problems with it). Diana [1] https://git-for-windows.github.io/ On 2 June 2016 at 15:43, Aaron Ballman via cfe-dev wrote: > On Wed, Jun 1, 2016 at 6:31 PM, Renato Golin wrote: >> I think we should start two other threads: one about git tooling on Windows >> and one about infrastructure problems migrating to git. > > Some developers on Windows prefer to use GUI tools like TortoiseSVN to > command line tools for version control. The last time I tried > TortoiseGit on Windows (which was over a year ago), it did not feel > ready for production use on a complex project to me (I had crashes on > simple operations, and it seems I was not alone in seeing flaky > behavior: https://gitlab.com/tortoisegit/tortoisegit/issues/1738 and > https://gitlab.com/tortoisegit/tortoisegit/issues/2494 as examples). > > Are there suitable GUI tools for git on Windows for projects as > complex as LLVM? I believe MSVC has some integration, but I've not > used it before. Perhaps other tools exist that match the integration > and stability that TortoiseSVN has with Explorer? > > I bring this up as a possible minor concern because asking people to > switch from one set of command line commands to another set of command > line commands is a different beast than asking people to switch from > Explorer-integrated menus and dialogs to the command line (that's a > drastically different workflow to achieve the same end result of > source code version control). > > ~Aaron > ___ > 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
