similar to: Request to merge r242372 into the 3.7 branch: Fix for C API incompatibility between 3.6 and 3.7.

Displaying 20 results from an estimated 6000 matches similar to: "Request to merge r242372 into the 3.7 branch: Fix for C API incompatibility between 3.6 and 3.7."

2015 Nov 09
2
Request to merge r242372 into the 3.7 branch: Fix for C API incompatibility between 3.6 and 3.7.
We covered this particular patch a bit at the C API BoF at the conference, and I think the general opinion is that this was just an unintentional bug and that fixing it is in 3.7.1 is the best solution forward. I'll send out more on the C API BoF as I get out from under a pile of email. -eric On Mon, Nov 9, 2015 at 2:07 PM Reid Kleckner <rnk at google.com> wrote: > We knew this
2015 Sep 06
2
LLVMBuildLandingPad is wrong on 3.7
Hi all, During the dev in between 3.6 and the release of 3.7, the personality function was moved from the landingpad to the function itself. During theses events, LLVMBuildLandingPad was changed, twice. The first time in a backward incompatible way, the second in a backward compatible way. As things are now, the backward incompatible way is in 3.7 and the backward compatible in master. Meaning
2015 Nov 21
11
[3.7.1 Release] -rc2 has been tagged
Hi, There was one problem in -rc1, so we had to do another release candidate. -rc2 has now been tagged and is ready for testing. -Tom
2015 Nov 17
12
3.7.1-rc1 has been tagged. Let's begin testing!
Hi, I have just tagged 3.7.1-rc1, so it is ready for testing. As a reminder, when doing regression testing, use the 3.7.0 release as your baseline. Thanks, Tom
2015 Nov 17
2
3.7.1-rc1 has been tagged. Let's begin testing!
John removed the assertion in his major alignment tracking patch. I manually did that on the branch in r253380. On Tue, Nov 17, 2015 at 1:10 PM, Hans Wennborg <hans at chromium.org> wrote: > On Mon, Nov 16, 2015 at 7:32 PM, Tom Stellard <tom at stellard.net> wrote: > > Hi, > > > > I have just tagged 3.7.1-rc1, so it is ready for testing. As a > > reminder,
2015 Nov 05
13
3.7.1 Release Update - Stable patches deadeline extended to November 9 - testers needed
Hi, I know a lot of people were busy with the dev-meeting last week, so I've decided to continue to accept stable patches until November 9. I would still like to keep the original schedule of an -rc1 release on November 10, so if there are any newly submitted patches that take more than a few days to get approved, they will probably end up going into llvm 3.7.2. I am currently working
2015 Jun 23
2
[LLVMdev] LLVM 3.7 release plan and call for testers
Daniel, Note the openmp library only has cmake build machinery preventing autoconf-based builds. Jack On Tue, Jun 23, 2015 at 10:18 AM, Daniel Sanders <Daniel.Sanders at imgtec.com> wrote: > Hi, > > I'll do Mips as usual. Are we going to do an autoconf-based build for LLVM 3.7? If so, I might try Mips64 packages too. > >> -----Original
2015 Dec 10
9
[3.7.1 Release] -final has been tagged.
Hi, I've tagged the final version of 3.7.1. There is no difference from 3.7.1-rc2, so testers just need to build the packages no testing is required. -Tom
2015 Jun 22
12
[LLVMdev] LLVM 3.7 release plan and call for testers
Hello everyone, Please let me know if you'd like to help providing binaries and testing for your favourite platform. If you were a tester on the previous release, I've bcc'd you on this email. I propose this schedule for the 3.7 release: - 14 July 2015: Create the release branch. - 14 July -- 21 July: Testing Phase I. RC1 binaries are built and tested. - 22 July -- 29 July: Fix
2016 Apr 22
6
3.8.1 Release Schedule
Hi, It's about time to start thinking about the 3.8.1 release. Here is a proposed release schedule: May 25 - Deadline to request a change be merged to the 3.8 branch. June 1 - Deadline to merge changes to the 3.8 branch. June 1 - 3.8.1-rc1 June 8 - 3.8.1-rc2 (if necessary) June 15 - 3.8.1 Release If you want a patch included in the 3.8.1 release, send an email to llvm-commits with the
2016 Jan 07
3
[3.7.1 Release] -final has been tagged.
Hmm, the clang+llvm-3.7.1-x86_64-sles11.3-linux-gnu.tar.xz tarball I uploaded doesn't seem to have made it on to this releases dir. I'm still a bit new to the process, is there a step that I skipped? On Wed, Jan 6, 2016 at 4:13 AM, Sedat Dilek via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Mon, Jan 4, 2016 at 9:59 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
2020 Mar 25
6
Bumping the CMake requirement for libc++ and libc++abi
On 03/25/2020 06:20 AM, Louis Dionne wrote: > > >> On Mar 25, 2020, at 00:47, Tom Stellard <tstellar at redhat.com> wrote: >> >> On 03/24/2020 09:00 PM, Petr Hosek via llvm-dev wrote: >>> In October, there was a discussion about updating CMake to 3.15: http://lists.llvm.org/pipermail/llvm-dev/2019-October/136295.html. No decision was made, but maybe we
2020 Mar 25
3
Bumping the CMake requirement for libc++ and libc++abi
On 03/24/2020 09:00 PM, Petr Hosek via llvm-dev wrote: > In October, there was a discussion about updating CMake to 3.15: http://lists.llvm.org/pipermail/llvm-dev/2019-October/136295.html. No decision was made, but maybe we should revisit that proposal? If we're going to require a newer version of CMake for some subprojects, I'd prefer to bump the minimum CMake version for all of LLVM.
2015 Dec 14
2
[cfe-dev] [3.7.1 Release] -final has been tagged.
> Polly fails on mips, s390x & powerpc (plenty of errors + a timeout: > http://paste.debian.net/343829/ ) Are the mips failures regressions? I haven't started building/testing polly yet so I don't know the current state of mips support for it. > -----Original Message----- > From: cfe-dev [mailto:cfe-dev-bounces at lists.llvm.org] On Behalf Of > Sylvestre Ledru via
2016 Feb 11
5
issues with split llvm libraries and llvmpipe and failing to load library
Hey, So in Fedora rawhide we are now building llvm 3.7.1 into the lots of little shared libraries format. However I'm running into a major problem with the fact that sometimes dlclose isn't dropping all the LLVM libraries from the address space of the process. We have a sequence like this: a) X server asks mesa gbm library to init, it loads the kms_swrast_dri.so with
2015 Nov 22
2
[cfe-dev] [3.7.1 Release] -rc2 has been tagged
Should I expect the "-openmp" to work for this RC? I got a link error (only in phase 3?). Maybe the fact that it happened in phase 3 suggests some hardware malfunction of mine? Or are there tests executed on phase 3 that aren't attempted on earlier phases? $ CC=clang CXX=clang++ ./test-release.sh -release 3.7.1 -rc 2 -j1 -openmp -triple armv7l-ubuntu15.10-linux-gnueabihf ... cd
2015 Jul 15
10
[LLVMdev] [3.7 Release] We have branched
Hi all, The 3.7 release branch was created from trunk at r242221 today (around 10:40 pm UTC). Branch policy: - Any doc changes can go in. Updates to the release notes are highly encouraged, and should be committed directly to the branch. - All other patches should be approved by the release manager (me) and the appropriate code owner. To get a change merged, commit it to trunk, and then reply
2017 Jan 25
2
LLVM 3.9.1 build race?
Hi Justin, > This looks like something I fixed recently, in r290271: ... ... > The tablegen build adopted USES_TERMINAL for this same reason in > r280748. I applied the 2 patches you mentioned above on my 3.9.1 tree and although the build seems to go along nicely than the earlier reported symptoms I can still see LLVMSupport being built a bit too many times than expected. $ cat
2015 Aug 28
2
[3.7 Release] 3.7.0-final has been tagged
On 28 Aug 2015, at 20:12, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Aug 27, 2015 at 6:46 PM, Hans Wennborg <hans at chromium.org> wrote: >> I have promoted RC4 to final; 3.7.0 has reached its final state. >> >> Thanks for all your hard work so far. Please build and upload binaries >> with "-final", and let's ship this next
2015 Aug 28
7
[3.7 Release] 3.7.0-final has been tagged
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