similar to: [LLVMdev] LLVM 3.4rc2 Binaries Now Available

Bill, et al., FYI, there are currently two issues that I'm tracking that should be fixed prior to release: 1. PowerPC self-hosting is currently broken(*), triggered by a change made to improve if conversion on ARM. There is a patch on the commits list that fixes problems seen by self hosting (and, if nothing else, that patch should likely go into 3.4), but I don't think that any of us

+grosbach Hi Hal, Re (1): Jim is our resident ARM expert. Adding him here. Re (2): There are a ton of simple programs that have been reported over the last month that are failing at higher levels. It's quite disturbing, really. I don't have a lot of time to debug these (it's no longer my main job to work on LLVM). I'll try to press people as much as possible. -bw On Wed, Dec

The LLVM 3.4 branches are now frozen. We’re only accepting major, super horrible bug fixes from now on. The testers are going to do a third phase of testing, but it’s mostly to verify that we don’t have any major problems left. Share and enjoy! -bw

Bill, et al., There are still a number of open bug reports demonstrating miscompiles on x86 with small/reduced test cases. I propose that we either delay this release until these have been fixed, or plan on a point release in the near future. I recommend that we put out another two release candidates, one at the end of this week, and one after another two weeks or so, to allow for these

On 2013-12-04 08:22, Bill Wendling wrote: > The LLVM 3.4rc2 binaries are now available for testing! Please download them and compile and test things. See if it breaks your code! Please file bugs for any issues you encounter. At this point, we’re only accepting fixes for regressions from 3.3. Cool. For convenience, here are the links http://llvm.org/pre-releases/3.4/rc2 -- /Jacob Carlborg

On 2018-01-10 17:26, Hans Wennborg via llvm-dev wrote: > Strange. Some of the files work for me, and some get the error message > you showed. I had a problem with the following files seven hours ago when my build failed. http://releases.llvm.org/3.9.0/clang+llvm-3.9.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz http://releases.llvm.org/3.9.1/clang+llvm-3.9.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz

On 2018-01-13 21:08, Anton Korobeynikov via llvm-dev wrote: > Jacob, > > We believe the issue is fixed now. Could you please confirm? It's still taking between 5 and 22 seconds to get a reply. -- /Jacob Carlborg

On 2017-12-30 21:27, Anton Korobeynikov via llvm-dev wrote: > Hello > > We are not planning to use git tags there (at least until the git > migration would happen). Please use the release branches. To me it doesn't matter if it's a tag or a branch, but, as far as I can see, there are no branches for point releases. For example, there's a branch release_50, but no branch

That’s a long laundry list of bugs there. It would be great to have them fixed, but the reality of the situation is that they won’t be fixed for weeks or more, if at all. And with Christmas coming up, it makes things even worse. There are a few days before Phase III starts to have some progress on them. But if they don’t make it, then we’ll have to release without them. -bw On Dec 12, 2013, at

On 2018-01-17 12:29, Anton Korobeynikov via llvm-dev wrote: > Which URL ? They all seem to be slow. But here's one example: https://releases.llvm.org/4.0.0/clang+llvm-4.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz -- /Jacob Carlborg

Jacob, We believe the issue is fixed now. Could you please confirm? On Sat, Jan 13, 2018 at 11:41 AM, Jacob Carlborg via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 2018-01-10 17:26, Hans Wennborg via llvm-dev wrote: >> >> Strange. Some of the files work for me, and some get the error message >> you showed. > > > I had a problem with the following files

This is strange and everything is fast for me. Let's continue off-list. On Wed, Jan 17, 2018 at 8:13 PM, Jacob Carlborg via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 2018-01-17 12:29, Anton Korobeynikov via llvm-dev wrote: >> >> Which URL ? > > > They all seem to be slow. But here's one example: > >

What's the status here? Can someone keep https://llvm.org/docs/Proposals/GitHubMove.html updated with the current status of things? And once things are usable, probably update https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo as well. On Wed, Oct 24, 2018 at 4:57 AM Jacob Carlborg via lldb-dev < lldb-dev at lists.llvm.org> wrote: > On 2018-10-24

On 2018-01-15 22:45, Anton Korobeynikov via llvm-dev wrote: > This should be fixed as of now. I just tried again, it takes over 60 seconds to get a reply. -- /Jacob Carlborg

I've noticed that there are no tags in any of the Git mirrors [1], [2] or [3]. Would it be possible to add the tags? [1] https://git.llvm.org/git/llvm.git [2] https://github.com/llvm-mirror/llvm [3] https://github.com/llvm-project/llvm-project-20170507 -- /Jacob Carlborg

On 2017-09-08 14:33, Brian Cain via llvm-dev wrote: > > Hans, > > Sorry it's a little late -- I got a request for ubuntu x86_64. > > Uploaded clang+llvm-5.0.0-linux-x86_64-ubuntu16.04.tar.xz and > clang+llvm-5.0.0-linux-x86_64-ubuntu14.04.tar.xz This one has a different name than all the other releases :(. The other releases are named

On 2018-09-20 10:01, Hans Wennborg via llvm-dev wrote: > Yes, it's a manual process. The binaries are build and tested by > volunteers, and the set of folks who volunteers differs a little > between releases. I would assume LLVM has some kind of CI infrastructure. That should be able to build the release binaries. > The pre-built binaries are really mostly for users who want to

On Nov 25, 2014, at 10:07 AM, Viswanath Puttagunta <viswanath.puttagunta at linaro.org> wrote: > > > Also is there plans to make the NEON optimisations on ARMv7 run time > > detectable like they have in cairo/pixman? For generic distributions > > it would nice to be able to be able to enable them as they offer > > decent performance improvements but have the code

On 2013-07-24 09:47, Tyler Hardin wrote: > Not much slower. VBox does an amazing job at getting near native > performance on modern machines (those with nested paging etc.). This is > definitely the best option if your computer has ~2g ram and 2+ cores. > Give the Ubuntu VM 2g and 1 (maybe 2) core/s and it should be fine. At work, it takes significantly longer to boot our Ruby on

On 6 February 2016 at 01:02, C Bergström <cfe-dev at lists.llvm.org> wrote: > I worked on the port of llvm-OpenMP-formally-known-as-Intel to Aarch64 > - can it be included there as well? (I'm not sure what's precisely > involved - I'm willing to do my best fixing any bugs which pop up - Hi Chris, That'd entail me enabling them for AArch64. I have to say, I've