similar to: [Release-testers] [cfe-dev] [4.0.0 Release] Relase Candidate 1 has been tagged

On Tue, Aug 1, 2017 at 3:01 AM, Simon Dardis <Simon.Dardis at imgtec.com> wrote: > Currently I'm getting "Couldn't write to remote file "/home/testers/uploads/clang+llvm-5.0.0-rc1-mips-linux-gnu.tar.xz": Failure", > does that account need more space? Yes, the partition is full. I've asked Anton to see if we can fix this.

Hi, I'm seeming new regressions form 4.0.0 for mips big endian: DataFlowSanitizer-mips64 :: custom.cc DataFlowSanitizer-mips64 :: propagate.c SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard-dso.cc SanitizerCommon-asan-mips-Linux :: sanitizer_coverage_trace_pc_guard.cc SanitizerCommon-asan-mips64-Linux :: Linux/getpwnam_r_invalid_user.cc

Hi, No major issues seen so far for mips. Binaries uploaded. SHA256(clang+llvm-6.0.0-rc3-mipsel-linux-gnu.tar.xz)= 6e4fab79cc341a9084dab94cced108daff39fcde14a11e8d7ae454e9f92cb77c SHA256(clang+llvm-6.0.0-rc3-mips-linux-gnu.tar.xz)= 54887a039d3d7ccff17a0c7245f4c9d778a1c22f96b619db554849da55293d61 SHA256(clang+llvm-6.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)=

Hi Hans, I'm seeing one unexpected failure: libc++ :: std/input.output/stream.buffers/streambuf/streambuf.protected/streambuf.put.area/pbump2gig.pass.cpp Test logs show: Standard Error: -- terminating with uncaught exception of type std::length_error: basic_string -- but only on my big endian MIPS machine. I have filed PR36373 for the above failure. I've looked at the failures

Hello everyone, Source, binaries and docs for LLVM-5.0.0-rc2 are now available at http://prereleases.llvm.org/5.0.0/#rc2 (I'll add more binaries as they become available.) Please try it out, run tests, builds your favourite projects and file bugs about anything that needs to be fixed (including docs!), marking them blockers of http://llvm.org/pr33849. Cheers, Hans

Dear testers, 6.0.0-rc3 was just tagged, after r325901 on the branch. There are still a few open blockers, but I'm not sure we'll actually end up blocking on all of them. So depending on what comes up, this release candidate is probably pretty close to what the final release will look like (I'm still hoping for more release notes, though). I'm hoping we can get to

Hi Hans, Looks ok here. I've uploaded the binaries. SHA256(clang+llvm-6.0.0-mipsel-linux-gnu.tar.xz)= 5ff062f4838ac51a3500383faeb0731440f1c4473bf892258314a49cbaa66e61 SHA256(clang+llvm-6.0.0-mips-linux-gnu.tar.xz)= 39820007ef6b2e3a4d05ec15feb477ce6e4e6e90180d00326e6ab9982ed8fe82 SHA256(clang+llvm-6.0.0-x86_64-linux-gnu-debian8.tar.xz)=

Hi, if I wanted to reproduce the official build, for example in order to get a code-signed Windows build [1], to which documentation can I turn to find out about the steps and tools (and their versions) used? That is, I am interested in the steps done by the respective maintainers which yield the packages at http://releases.llvm.org/download.html Thanks and with best regards, Oliver [1] I

Hi Oliver, If you look at http://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library that lists the tools and minimum version required. There is some documentation for how to build a release: http://llvm.org/docs/ReleaseProcess.html For the official windows builds, Hans Wennborg provides the batch file used to create any given upload when he reports on the

Dear testers, There's been a lot of merges since rc1, and hopefully the tests are in a better state now. 6.0.0-rc2 was just tagged, after r324506. Please test, let me know how it goes, and upload binaries. Thanks, Hans

Very cool initiative! Thank you! On Fri, Jan 20, 2017, at 10:59 AM, Mehdi Amini via cfe-dev wrote: > Hi, > > FYI, I added a Green dragon job to build and test (stage 1 only right > now) the release branch: > http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA-release-4/ > <http://lab.llvm.org:8080/green/job/clang-stage1-configure-RA-release-4/> > > — >

Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues remain. I know we're a little bit behind schedule, but hopefully we can get to 'final'

All, I upgraded to the [*] stable release branch. When I call into the box (confirmed on 2 installations) the caller no longer hears the ringing. The CLI confirms that extensions are being 'rung'. Whassup? Willy Willy Wouters ypOne Publishing

Hi All, Can I have the release plan of OCFS R1.0.15? Our big Customer, *** BANK, has hit BUG:4590449 (fixed in R1.0.15) and we need to show our ETA of R1.0.15 now. # Customer's system is running on RH 2.1 x86. Since OCFS R2.0 has already been released, I'm afraid that R1.0.15 will be released or not. (R1.0.14 is terminal release?) Any information will be helpful for us. Regards,

Hi All, Can I have the release plan of OCFS R1.0.15? Our big Customer, *** BANK, has hit BUG:4590449 (fixed in R1.0.15) and we need to show our ETA of R1.0.15 now. # Customer's system is running on RH 2.1 x86. Since OCFS R2.0 has already been released, I'm afraid that R1.0.15 will be released or not. (R1.0.14 is terminal release?) Any information will be helpful for us. Regards,

This is a very simple question but I couldn't form a site search quesry that would return a reasonable result set. Say I have a vector: x <- c(0,2,3,4,5,-1,-2) I want to replace all of the values in 'x' with the log of x. Naturally this runs into problems since some of the values are negative or zero. So how can I replace all of the positive elements of x with the log(x) and the

Dear testers, The final version of 6.0.0 has just been tagged from the branch after r326550. It has the same contents as -rc3 modulo release notes and one small x86 fix (r326393). Please build the final binaries and upload to the sftp. For those following along: this means llvm-6.0.0 is complete, but it will take a few days to get all the tarballs ready and published on the web page. I will

Hi A few days ago I upgraded debian8 to debian9 dovecot is from source # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24.2 (aaba65b7) # OS: Linux 4.9.0-13-amd64 x86_64 Debian 9.13 Today I get some times in logs: "dovecot-uidlist line 112: Invalid data" and I dont know why This is claster dovecot: dovecot1 - debian8 dovecot2 - debian8 dovecot3 - debian8

Thanks, that sounds like it would work. Was this based on what any other target did? Or do any other targets take this approach? I just want to make sure that we don't already have a hook suitable for this. Overriding runOnFunction to run what could be described as just a "late SelectionDAG pass" sounds pretty intrusive. Do you remember other approaches that didn't work? --

Oh, one thing I forgot to mention: ReadOnly objects are also counted as small data globals on PPC (on top of BSS, Data, Common). That's what the r2 base is for (.sdata2, defined to be constant data). 32-bit immediate loads take 2 ops minimum on PPC, so even constant loading benefits from small data. It'd be handy to add a third argument containing what kind would normally be returned: