search for: llvmorg

...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*) /usr2/seaswara/work/llvmorg/llvm-build/../lib/Support/Unix/Signals.inc:422:15 #1 0x4b136b PrintStackTraceSignalHandler(void*) /usr2/seaswara/work/llvmorg/llvm-build/../lib/Support/Unix/Signals.inc:481:1 #2 0x4b2ee4 SignalHandler(int) /usr2/seaswara/work/llvmorg/llvm-build/../lib/Support/Unix/Signals.inc:198:60 #3 0x7fd12664...

As first discussed in the giant "New LLVM git repository conversion prototype" thread, I've pushed a git tag that allows git-describe to be used for generating human readable commit names on master. The tag is "llvmorg-10-init", to be interpreted as "the initial commit with major version number 10". The idea is to add similar tags along with future version bumps. git describe generates a name like this: $ git describe a4783ef llvmorg-10-init-8348-ga4783ef58d3 Where "llvmorg-10-init" is...

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" (here: "rc1" without dash) string in...

...rors occurred! See also "/home/elux/build/CMakeFiles/CMakeOutput.log". See also "/home/elux/build/CMakeFiles/CMakeError.log". === snap === Commands used: === snip === VERSION=8.0.1 DESTDIR=/tmp/llvm PREFIX=/usr/local #wget https://github.com/llvm/llvm-project/releases/download/llvmorg-${VERSION}/llvm-${VERSION}.src.tar.xz #wget https://github.com/llvm/llvm-project/releases/download/llvmorg-${VERSION}/cfe-${VERSION}.src.tar.xz #wget https://github.com/llvm/llvm-project/releases/download/llvmorg-${VERSION}/libcxx-${VERSION}.src.tar.xz #wget https://github.com/llvm/llvm-project/rel...

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 https://github.com/llvm/llvm-pro...

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 https://github.com/llvm/llvm-pr...

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 “compiler-rt-10.0.0.src.tar.xz”, is there anyway to figure out where does this tarball come from , and which was the corresponding COMMIT in the compiler-rt’s git repo? Another example: It seems we use different compi...

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

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

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

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

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

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 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 'final' on Monday. Testers, if you still have cyc...

...s. 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 used the "llvmorg-10.0.1-rc1" Git tag to build my llvm-toolchain on Debian/testing AMD64. Thanks. Regards, - Sedat - [1] https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.1-rc1

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 > > https://github.com/llvm/llvm-project/releases/tag/llvmorg-10.0.0-rc5 > > > > If nothing new comes up, I p...

Hi Tom, I would like to have the patch "Make LLVM_APPEND_VC_REV=OFF affect clang, lld, and lldb as well." for the "release/10.x" Git. That patch applies cleanly against latest "release/10.x" Git. Does that fit your criteria and if yes - what do I have to do? Thanks. Regards, - Sedat - [1]

...orries me the most. > > > > > > How large is a typical patch to merge that is backported from the next > major release to a previous dot release? > > The diffs are usually fairly small, but there can be many. For 8.0.1 > there were about 60 patches merged (git log > llvmorg-8.0.0..llvmorg-8.0.1 --oneline | wc -l). (For 9.0.0 I think > we're approaching 200 merges.) > > Depending on when the rename happens, I guess it could affect merges > either for a major release or for a dot release, and it would mean a > lot of extra work unless there was some t...

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 cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> wrote: > > On...

...gt; > > But the version-strings look odd. > > > > You shouldn't have to make any changes to the source, did you > try running the test-release.sh script? > I tried... $ ./llvm/utils/release/test-release.sh -release 10.0.1 -rc 1 -triple x86_64-linux-gnu # Using git ref: llvmorg-10.0.1-rc1 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 137 100 137 0 0 345 0 --:--:-- --:--:-- --:--:-- 345 100 25.7M 0 25.7M 0 0 2263k 0 --:--...