similar to: Tag for using git describe on master

Hypothetically assume that we have an LLVM release X and want to rename variables in the next major release Y. In order to backport patches from Y to X.1 smoothly, I think we could first apply the automated renaming tool to X and then cherry-pick patches from Y. The obvious issue of doing this is, even though X.1 is a dot release, a very large number of lines would be changed from X, though. On

On Mon, Sep 9, 2019 at 8:25 PM Hans Wennborg <hans at chromium.org> wrote: > On Fri, Sep 6, 2019 at 6:17 PM Björn Pettersson A via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > I'm a little bit curious to hear more about the experiences from the > changes in LLD. > > I’m thinking about things like: > [..] > > - merging of bugfixes to older

Hi Rui, Not sure if you have seen this problem, but I have been running into this problem when I run the lld tests and the failure occurence is once in 5 times. lld: ../tools/lld/lib/Core/Resolver.cpp:402: void lld::Resolver::deadStripOptimize(): Assertion `symAtom' failed. #0 0x4b05ae llvm::sys::PrintStackTrace(_IO_FILE*)

Hi Tom, can you change your release process in concerns of "RC" releases at naming convention? [ Example ] Git Tag: "llvmorg-10.0.1-rc1" llvm-project prerelease tarball: "llvm-project-10.0.1rc1.tar.xz" The release Git tag is called "llvmorg-10.0.1-rc1" (here: "-rc1" with dash) but the provided prerelease tarballs have "10.0.1rc1"

Hi folks! I'm trying to build LLVM with LLVM on Ubuntu using the commands below. Building it with the GNU stuff (cpp, gcc, g++ and binutils packages) works, but after removing it, moving LLVM to /usr/local and symlinking /usr/bin/ld to ld.lld, I'm getting the following: === snip === -- The C compiler identification is Clang 8.0.1 -- The CXX compiler identification is Clang 8.0.1 -- The

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

Hello everyone, It took a bit longer than planned, but Release Candidate 3 is now here. It was tagged as llvmorg-10.0.0-rc3 on the release branch at 3a843031a5 and contains 95 commits since the previous release candidate. If no new problems arise, this is what the final release will look like. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc3 and

Hello everyone, After some delay, the llvmorg-11.0.0-rc3 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc3 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc3 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:

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

Hi Tom, thanks and congrats for LLVM 10.0.1-rc1 release. [1] shows 2 assets. 10.0.0 RCs had a lot of more assets. I am missing the llvm-project-10.0.1rc1.tar.xz tarball. Will you provide them later or is there a new development/workflow decision I do not know of? BTW, the source zip and tar.gz tarballs show no sizes. I am using Mobile LTE/UMTS to download stuff from the Internet. For now I

On Sun, Mar 22, 2020 at 9:05 PM Andrew Kelley <andrew at ziglang.org> wrote: > > On 3/19/20 9:51 AM, Hans Wennborg via llvm-dev wrote: > > Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the > > release branch at 35627038123. > > > > Source code and docs are available at > > https://prereleases.llvm.org/10.0.0/#rc5 and > >

Hello again, We had to pick up another bug fix, so here is another release candidate: llvmorg-11.0.0-rc5 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc5 Pre-built binaries will be added as they become ready. Please file reports for any bugs you find as blockers of

Hello everyone, Release Candidate 4 was tagged earlier today as llvmorg-10.0.0-rc4 on the release branch at b406eab8880. It contains 12 commits since the previous release candidate. If no new problems arise, this is what the final release will look like. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc4 and

Hi there, Do we have any plan to add release tags to the compiler-rt git repo, say http://llvm.org/git/compiler-rt ? Without a release tag I’m not sure which version of compiler-rt the llvm-project is using. Take “LLVM 10.0.0 Release”( https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0) as an example: The tarball of compiler-rt been used in this version is

Hello everyone, Release Candidate 2 was tagged earlier today as llvmorg-10.0.0-rc2. It includes 98 commits since the previous release candidate. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc2 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc2 Pre-built binaries will be added as they become available. Please file bug reports for any issues

What is the proper solution to disable auto-vectorization for unaligned data? I have an out of tree target and I added this: bool OpusTargetLowering::allowsUnalignedMemoryAccesses(EVT VT, bool *Fast) const { if (VT.isVector()) return false; .... } After that, I could see that vectorization is still done on unaligned data except that llvm will copy the data back and forth from the source

On 01/14/2020 08:59 AM, Russell Gallop wrote: > Hi Tom, Hans, > > I can't see LLVM-9.0.1-win*.exe from Hans on the GitHub release page (https://github.com/llvm/llvm-project/releases/tag/llvmorg-9.0.1). Is this still in progress? > Hans did you upload these? I don't see them on the server. -Tom > Thanks > Russ > > On Thu, 9 Jan 2020 at 20:05, Tom Stellard via

On Wed, May 20, 2020 at 11:12 PM Tom Stellard <tstellar at redhat.com> wrote: > > On 05/20/2020 09:53 AM, Sedat Dilek wrote: > > On Wed, May 20, 2020 at 5:06 PM Tom Stellard <tstellar at redhat.com> wrote: > >> > >> On 05/19/2020 09:05 PM, Sedat Dilek wrote: > >>> Hi Tom, > >>> > >>> thanks and congrats for LLVM

Hello again, I had hoped that rc4 would be the last one, but I wanted to pick up one more fix, so here we go. Release Candidate 5 was just tagged as llvmorg-10.0.0-rc5 on the release branch at 35627038123. Source code and docs are available at https://prereleases.llvm.org/10.0.0/#rc5 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 If nothing new comes up, I plan to tag

Dear All, Recently, I wanted to reinstall a fresh copy of llvm for a new project I am working on. However I ran into the following issue when attempting to build a vanilla copy. CommandLine Error: Option 'mc-relax-all' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options make[2]: ***