similar to: 7.0.1-rc2 release has been tagged please begin testing

Displaying 20 results from an estimated 1000 matches similar to: "7.0.1-rc2 release has been tagged please begin testing"

2018 Nov 27
3
apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7
Who maintains apt.llvm.org? On 11/27/18 9:25 AM, Andrew Kelley wrote: > ---------- Forwarded message --------- > From: Andrew Kelley <superjoe30 at gmail.com> > Date: Mon, Nov 26, 2018 at 10:38 AM > Subject: apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7 > To: LLVM Dev <llvm-dev at lists.llvm.org> > > > This build worked on Nov 24 and
2018 Nov 29
2
apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7
It appears that there was an out-of-band patch from Samuel Thibault: https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/blob/7/debian/patches/D54378-hurd-triple.diff Although the patch was approved here https://reviews.llvm.org/D54378 Is this patch going to land in 7.0.1 or 8? kristopher > Here's further proof: > > wget >
2018 Dec 08
5
LLVM 7.0.1-rc3 has been tagged.
Hi, I've just tagged 7.0.1-rc3. This will hopefully be the last release candidate. Please test and report results. Thanks, Tom
2018 Dec 20
5
7.0.1-final has been tagged
Hi, I've tagged the 7.0.1 final release. Testers may begin uploading binaries. -Tom
2018 Dec 24
2
[Release-testers] 7.0.1-final has been tagged
Ubuntu and SLES tarballs uploaded. I haven't had a chance to make a SLES12 build yet, but I will try in the coming days. f7553a0d66092ca0bbe1eab2af405523a18bafba clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-18.04.tar.xz 41db01a3b216df4fc22fae9c44e248889f9a01ed clang+llvm-7.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz caf149635742622a3a5b220146ff34f9202b8670
2019 Jan 09
2
[Release-testers] [cfe-dev] 7.0.1-final has been tagged
On 01/08/2019 11:36 AM, Ian Tessier via Release-testers wrote: > Can the ubuntu tarballs be published to the download site? They're not available yet. > These are up on the download site now. -Tom > On Mon, Dec 24, 2018 at 7:38 AM Brian Cain via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > Ubuntu and SLES tarballs
2018 Aug 03
10
[7.0.0 Release] rc1 has been tagged
Dear testers, 7.0.0-rc1 was just tagged (from the branch at r338847). It's early in the release process, but I'd like to find out what the status is of the branch on our various platforms. Please run the test script, share the results, and upload binaries. Thanks, Hans
2018 Aug 22
7
[7.0.0 Release] rc2 has been tagged
Dear testers, 7.0.0-rc2 was just tagged (from branch revision r340437). There have been a bunch of merges since rc1, and hopefully many of the issues with the previous candidate are fixed in this one. Please run the test script, share the results, and upload binaries. I will publish source tarballs, docs, and binaries on the web page once they're ready. Thanks, Hans
2019 Mar 12
6
[8.0.0 Release] rc5 has been tagged
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.
2018 Nov 29
2
apt.llvm.org has the wrong binaries/headers for llvm-toolchain-xenial-7
On 11/28/18 8:46 PM, Friedman, Eli via llvm-dev wrote: > On 11/28/2018 5:28 PM, Kristopher Tate via llvm-dev wrote: >> Although the patch was approved here https://reviews.llvm.org/D54378 >> >> Is this patch going to land in 7.0.1 or 8? > > For trunk (and therefore 8), looks like it was approved, and it's just > waiting for someone with commit rights to merge it.
2018 Jul 25
2
are the LLD libraries thread safe?
E.g. Is it intended to be allowed to call lld::elf::link in 2 different threads at the same time? Follows is an example Valgrind error I ran into when doing the above. I'll try putting a global resource lock on invoking LLD and see if it solves the problem. ==5467== Invalid write of size 8 ==5467== at 0x525509: llvm::DenseMapBase<llvm::DenseMap<llvm::CachedHashStringRef, int,
2018 Sep 10
15
[7.0.0 Release] rc3 has been tagged
Dear testers, 7.0.0-rc3 was just tagged (from branch revision r341805). No further release candidates are currently planned, so this is a release candidate in the real sense: unless any serious issues surface, this is what the final release will look like. Please run the test script, share your results and upload binaries. Please also take a look at the release notes and other docs; small
2017 Sep 17
4
assertion triggered since update to llvm 5
So, 90% of the time I've seen this, it was memory corruption, usually use after free. I know I fixed one after 5.0 branched. You should compile with address sanitizer enabled, and I suspect you will find the issue quicky. If not, we really need ir that reproduces it. On Sun, Sep 17, 2017, 12:27 PM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think I forgot to
2017 Sep 16
2
assertion triggered since update to llvm 5
When zig updated to llvm 5 we started hitting this assertion: zig: /home/andy/downloads/llvm-project/llvm/include/llvm/Support/Casting.h:106: static bool llvm::isa_impl_cl<To, const From*>::doit(const From*) [with To = llvm::Instruction; From = llvm::Value]: Assertion `Val && "isa<> used on a null pointer"' failed. I wonder if however this was caused by an
2017 Sep 17
2
assertion triggered since update to llvm 5
Can you please open a bug on bugzilla and attach the ir testcase? Your fix doesn't look right (just hiding the assertion failure) On Sep 17, 2017 10:45 AM, "Andrew Kelley via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > What do you think about this patch? > > --- a/llvm/lib/Transforms/Scalar/NewGVN.cpp > +++ b/llvm/lib/Transforms/Scalar/NewGVN.cpp > @@
2018 Jul 25
2
are the LLD libraries thread safe?
Hi Andrew, LLD relies on various bits of global state which are manipulated during the link, so I wouldn't expect it to be thread safe at that level, although it does attempt to reset that global state at the start of each call to link(), so it should be callable sequentially. Regards, James On 25 July 2018 at 02:37, Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote:
2018 Jan 06
2
status on NewGVN?
Greetings, I just found a bug in NewGVN: https://bugs.llvm.org/show_bug.cgi?id=35839 I noticed that it's off by default in clang. I'm going to turn it off by default in zig too, since it has a bug. What's the current status? Are we trying to move towards using it by default in llvm 6.0.0? 7.0.0? Regards, Andrew Kelley http://ziglang.org/ -------------- next part -------------- An
2018 Sep 17
8
[7.0.0 Release] The final tag is in
Dear testers, The final version of 7.0.0 has been tagged from the branch at r342370. It is identical to rc3 modulo release notes and docs changes. Please build the final binaries and upload to the sftp. For those following along: this means 7.0.0 is done, 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
2020 Jul 28
11
[11.0.0 Release] Release Candidate 1 is here
Hello everyone, We're a little bit behind schedule, but RC1 is now here. It was tagged earlier today as llvmorg-11.0.0-rc1. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc1 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc1 Pre-built binaries will be added as they become available. Please file bug reports for any issues you find as
2018 Aug 06
4
[Release-testers] [7.0.0 Release] rc1 has been tagged
On Sun, Aug 5, 2018 at 5:49 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 3 Aug 2018, at 13:37, Hans Wennborg via Release-testers <release-testers at lists.llvm.org> wrote: >> >> 7.0.0-rc1 was just tagged (from the branch at r338847). >> >> It's early in the release process, but I'd like to find out what the >> status is of the branch