similar to: [LLVMdev] [3.5 Release] Branch Policy

Hi, I noticed that the LLVM 3.5 release branch landed recently. I have a few patches (these are all part of my recent work to fix up the CMake interface) that I'd like in both LLVM3.5 release branch and trunk that I'd like to commit Is there any policy on how should do this be done, or can I just commit the patch to both trunk and then the release branch with identical commit messages?

Dear everyone, The in-progress release notes for 3.7 [1,2] make it look like we didn't do very much over the past six months. Obviously that's not the case at all, so let's get them in shape! If you've been thinking "I should probably add this to the release notes at some point", now is the time :-) I have a list below of changes that might be worth mentioning. I

Bill, I have the openmp support in llvm 3.5svn now built on 10.7 using Xcode 4.6.3 and 10.8/10.9 using 5.1.1. The 10.7 build required the hack… perl -pi -e 's|list\(APPEND SANITIZER_COMMON_SUPPORTED_DARWIN_OS iossim\)||g' projects/compiler-rt/CMakeLists.txt to suppress building libclang_rt.asan_iossim_dynamic.dylib. The compiler-rt build now expects the iPhoneSimulator7.0.0.sdk but

I am pleased to announce that LLVM 7 is now available. Get it here: https://llvm.org/releases/download.html#7.0.0 The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets,

I am pleased to announce that LLVM 7 is now available. Get it here: https://llvm.org/releases/download.html#7.0.0 The release contains the work on trunk up to SVN revision 338536 plus work on the release branch. It is the result of the community's work over the past six months, including: function multiversioning in Clang with the 'target' attribute for ELF-based x86/x86_64 targets,

On Fri, Aug 3, 2018 at 3:38 PM, <paul.robinson at sony.com> wrote: > Hi Hans, > > I was just trying to push a release note about DWARF v5 support. I did: > git checkout release_70 # in the monorepo > git commit <update to llvm/docs/ReleaseNotes.rst> > git llvm push > but that fails. How do you want to do release notes? I'm not familiar with "git

Alex, I have built ubuntu binaries for the last couple of releases. I apologize -- I haven't built those new binaries yet, I only have uploaded the SLES ones. I have an ubuntu 14 tarball that I'll upload today. I will work on getting ubuntu 16 or 17 next. The dpkg/APT repos might be a good substitute, though. Hans, apologies -- I should've asked to hold the 7.0.0 release for

Ubuntu 16: a2a2768b04e1d561e6f9a1a2d525eda7aae18624 clang+llvm-7.0.0-x86_64-linux-gnu-ubuntu-16.04.tar.xz On Thu, Sep 20, 2018 at 7:12 PM Brian Cain <brian.cain at gmail.com> wrote: > Uploaded ubuntu 14: > > dec5ca53043c80c1c6e90c0473df84f0182d80af > clang+llvm-7.0.0-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > > On Wed, Sep 19, 2018 at 12:58 PM Brian Cain <brian.cain

On Wed, Dec 03, 2014 at 11:51:07AM -0800, Michael Zolotukhin wrote: > Hi Tom, > > I also have several patches that might be useful in 3.5.1. They all are stability fixes: > > r221009: Correctly update dom-tree after loop vectorizer. > r222451: Fix a trip-count overflow issue in LoopUnroll. > r223170 and r223171: PR21302.Vectorize only bottom-tested loops. > Hi Arnold,

On Mon, Apr 14, 2008 at 2:50 PM, Edward Lee <eslee3 at uiuc.edu> wrote: > On Mon, Apr 14, 2008 at 5:37 PM, Chris Lattner <sabre at nondot.org> wrote: > > The code generator does CFG simplification to handle cases where blocks > > become dead during lowering. > Oh... is there a way to prevent that from happening? While %x is > always 1 and %T is always taken,

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

On Mon, Apr 14, 2008 at 5:37 PM, Chris Lattner <sabre at nondot.org> wrote: > The code generator does CFG simplification to handle cases where blocks > become dead during lowering. Oh... is there a way to prevent that from happening? While %x is always 1 and %T is always taken, %F isn't actually dead. There would be a way (with another intrinsic) for control to flow into %F at

Hi Hans, we have uploaded tarballs for ARM and AArch64 targets: a20ea3fe482e754a61ccb37c67456ad1 clang+llvm-6.0.1-aarch64-linux-gnu.tar.xz f37b132c3dfb3b776524980be5af3a76 clang+llvm-6.0.1-armv7a-linux-gnueabihf.tar.xz and 47a9a9bb02d41581e6804b98918188f6 clang+llvm-7.0.0-aarch64-linux-gnu.tar.xz e639d8f5dc58be5cf44d017fd5eefd6c clang+llvm-7.0.0-armv7a-linux-gnueabihf.tar.xz Yvan On Mon,

On Sat, Nov 29, 2014 at 08:34:34PM +0100, Dimitry Andric wrote: > On 29 Nov 2014, at 02:48, Tom Stellard <tom at stellard.net> wrote: > > On Wed, Nov 26, 2014 at 07:44:20PM +0100, Dimitry Andric wrote: > ... > >> I would like to propose the following additional patches for 3.5.1. These will already be part of the upcoming clang 3.5.0 import into the FreeBSD 11.0 base

On Wed, Aug 26, 2015 at 4:43 PM, Hans Wennborg <hans at chromium.org> wrote: > 3.7.0-rc4 has just been tagged. It is identical to rc3, plus: > > - r245902: Revert r245355: change of clang-tools-extra symlink in the > release script > - r245947: Merge of r245927: Fix LLDB build on MIPS > - r245948: Deprecate the DataLayout on the TargetMachine, and backport > the 3.8 API

LLVM devs: Is this the right forum for nominating a fix for the 3.9 branch? I'd like to nominate r279930. http://llvm.org/viewvc/llvm-project?view=revision&revision=279930 We ran into this on 3.9.0, and then confirmed that it affects 3.7.0. Eric

Hi all: I am working on a project using llvm and we need to deal with multithreaded applications. I wanted to know if there was a C front end for llvm that could parse multithreaded applications? I tried llvm-gcc (4.2) and could not get it to work. Is there an extra parameter that I need to pass or something ? Thanks a lot for your help. Regards -- -- Aparna Graduate Student Department

Please review and comment about: http://llvm.org/docs/ReleaseNotes.html If we forgot anything or if there are edits, please commit them or let me know. Thanks! -Chris

Hi Dan, You can commit it to ReleaseNotes.rst on the branch directly, or send me a patch or just some text and I'll do it for you. Thanks, Hans On Mon, Jan 8, 2018 at 8:31 AM, Dan Liew <dan at su-root.co.uk> wrote: > Hi Hans, > >> To get a change committed to the branch, first commit it to trunk as >> usual, and then request it to be merged --- ideally by filing a

Dear testers, 3.7.0-rc4 has just been tagged. It is identical to rc3, plus: - r245902: Revert r245355: change of clang-tools-extra symlink in the release script - r245947: Merge of r245927: Fix LLDB build on MIPS - r245948: Deprecate the DataLayout on the TargetMachine, and backport the 3.8 API - Changes to the ReleaseNotes. Those changes should all be safe, and I expect this to be an extremely