search for: release_80

On Fri, Feb 8, 2019 at 9:53 AM Paweł Sikora via cfe-dev < cfe-dev at lists.llvm.org> 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 > > > (...)/clang++ -fPIC -target x86_64-linux-gnu --sysroot=(...) -march=x86-64 > -fuse-ld=lld -D_LIBCPP_...

Dear testers, 8.0.0-rc2 has been tagged from the release_80 branch at r353413. 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

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, a...

Dear testers, 8.0.0-rc3 was just tagged from the release_80 branch at r355015. We're running a little behind schedule now, but I think we're also close to be able to call this done. Please take a close look at this release candidate. Unless anything bad comes up, this is probably very similar to what the final release will look like. Testers, ple...

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 day...

Hans Wennborg wrote: >Dear testers, > >8.0.0-rc4 was just tagged from the release_80 branch at r355690. I've tested the current branch on SystemZ without problems. I noticed I forgot to send a ReleaseNotes updates, sorry. If there's still time, here's a list of the major user-visible changes: (See attached file: systemz-releasenotes.diff) Mit freundlichen Gruessen...

...compiler-rt between LLVM 9.0.1 Release and LLVM 9.0.1-rc1 Release, ``` # md5sum and tarball name 15f234da3e9a7f2a50173c1c95a6436e compiler-rt-9.0.1rc1.src.tar.xz 1b39b9b90007a2170ebe77d6214ec581 compiler-rt-9.0.1.src.tar.xz ``` Does these tarball all from branch release_90(there are also branch release_80, release_70, etc)? If so, which commit was picked by the different llvm release? Thanks, Hu Keping -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200415/8144ceaa/attachment.html>

...Browsed further down the page and followed the qualification branch install procedure. - Everything installed without any error or warning. - Typing afterwards in the terminal: "clang-8 --version" results in this return: clang version 8.0.1-svn363027-1~exp1~20190611211629.77 (branches/release_80) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin - Running in the terminal the configure command for GHDL:          "../configure --with-llvm-config=/usr/bin/llvm-config-8 --prefix=/opt/Ghdl"   results in this output: Use full IEEE library Build machine is: x86...

Hi folks, I want to update the Release Notes for the release/9.x, but seems like 'git llvm push' only supports commits to the master/trunk. What's the current process for such patches? Thanks, Alex. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: Message signed with OpenPGP URL:

...at commits are involved? In SVN revisions, it's the following: 351657 351658 351659 351660 351661 351662 351663 351799 351800 351801 351811 351931 351934 351946 351947 351948 In a git mirror, it's trivial to find these commits with the following command: git log $(git merge-base origin/release_80 master)..master tools/llvm-objcopy/COFF test/tools/llvm-objcopy/COFF Among these commits, there's one cycle of "Implement --add-gnu-debuglink", "Revert 'Implement --add-gnu-debuglink'", "Reapply: Implement --add-gnu-debuglink", "Remove testcase debu...

...e if it's there too. > > I can pass along logs if anyone wants to investigate. > > On Thu, Feb 7, 2019 at 9:41 AM Hans Wennborg via Release-testers < > release-testers at lists.llvm.org> wrote: > >> Dear testers, >> >> 8.0.0-rc2 has been tagged from the release_80 branch at r353413. >> >> 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 >> _____...

...ntly added -Wunreachable-code to our set of warnings.  The problem I am seeing is the compile fails with (valid) unreachable code warnings on the slave, but passes (no warning) locally.  All machines have the same compiler version clang version 8.0.1-svn369350-1~exp1~20190820121219.79 (branches/release_80) Distcc takes the compile line, removes -o <output> and replaces it with -E and sends the preprocessed result to the slave where it is compiled without any -I, -isystem or -D options. Generating the preprocessed output and compiling it locally finds the warnings.  I'm concerned that...

...d about moving Risc-V out of experimental but I think it didn't go anywhere? Separately, do the listed patches sound okay for merging? Thanks, Hans On Fri, Jan 25, 2019 at 4:40 PM Bruce Hoult <brucehoult at sifive.com> wrote: > > In https://llvm.org/svn/llvm-project/llvm/branches/release_80 I find > that RISCV is still in LLVM_EXPERIMENTAL_TARGETS_TO_BUILD. not > LLVM_TARGETS_TO_BUILD. I thought people had agreed to change that in > this release? > > There are also at least a couple of fairly important patches that it > would be good to get back-ported into the relea...

...;+fxsr,+mmx,+sse,+sse2,+x87" "unsafe-fp-math"="false" "use-soft-float"="false" } !llvm.module.flags = !{!0} !llvm.ident = !{!1} !0 = !{i32 1, !"wchar_size", i32 4} !1 = !{!"clang version 8.0.0-svn356034-1~exp1~20190313093039.54 (branches/release_80)"} Thank you, Digvijay -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190407/5bc769cf/attachment.html>

On Tue, 15 Jan 2019, Hans Wennborg wrote: > On Sat, Jan 12, 2019 at 12:49 AM Jordan Rupprecht <rupprecht at google.com> wrote: >> >> >> >> On Fri, Jan 11, 2019 at 6:26 AM Martin Storsjö <martin at martin.st> wrote: >>> >>> Hi, >>> >>> The COFF support in llvm-objcopy is in a pretty half-finished state at the >>>

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

On Thu, Dec 13, 2018 at 7:18 AM Alex Bradbury via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, 13 Dec 2018 at 15:07, Hans Wennborg via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > On Thu, Dec 13, 2018 at 3:34 PM James Y Knight <jyknight at google.com> > wrote: > > > > We don't *need* it, no. But it might be useful. >