search for: release_39

...t; >>> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >>> >>> >>>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>>> >>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: >>>> >>>> #define COMPILE_TIME_ASSERT( expr ) \ >>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); >>>...

...Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >>>> >>>> >>>>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>>>> >>>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: >>>>> >>>>> #define COMPILE_TIME_ASSERT( expr ) \ >>>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); &...

> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: > > >> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: >> >> #define COMPILE_TIME_ASSERT( expr ) \ >> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); >> >> I notice that t...

....com> wrote: > > >> On Dec 23, 2016, at 11:17, Frédéric Riss <friss at apple.com> wrote: >> >> >>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: >>> >>> #define COMPILE_TIME_ASSERT( expr ) \ >>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); >>> >>&...

> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: > > #define COMPILE_TIME_ASSERT( expr ) \ > extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); > > I notice that the issue is fixed o...

...<friss at apple.com> wrote: >>>>>> >>>>>> >>>>>>> On Dec 22, 2016, at 9:36 PM, Jeremy Huddleston Sequoia via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>>>>>> >>>>>>> 3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: >>>>>>> >>>>>>> #define COMPILE_TIME_ASSERT( expr ) \ >>>>>>> extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attri...

3.9.0 and current release_39 (r90413) have issues with older static assertion macros like this one from an older libunwind: #define COMPILE_TIME_ASSERT( expr ) \ extern int compile_time_assert_failed[ ( expr ) ? 1 : -1 ] __attribute__( ( unused ) ); I notice that the issue is fixed on current trunk. Does a...

...y such variables first. - Is there a configuration in the CI matrix that builds all of LLVM with ThinLTO so that I can be reasonably sure any error is most likely local to my environment or because of operator (silly me) faults? $ svn info URL: http://llvm.org/svn/llvm-project/llvm/branches/release_39 Relative URL: ^/llvm/branches/release_39 Repository Root: http://llvm.org/svn/llvm-project Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 Revision: 290054 Node Kind: directory Schedule: normal Last Changed Author: tstellar Last Changed Rev: 288847 I also pass these in LDFLAGS but they'...

...s, do you want to mention the removal of the CppBackend? - Chris Dewhurst, do you want to mention soft-float SPARC support (and potentially other SPARC improvements)? - Benjamin, should we mention include-fixer somewhere? Many thanks, Hans [1] http://llvm.org/viewvc/llvm-project/llvm/branches/release_39/docs/ReleaseNotes.rst?view=markup

I just built a stage-1 compiler from the 3.9 release bits and built the lldb from head sources which worked fine. Let me try again using 3.9 build compiler to build 3.9 bits. Teresa On Tue, Sep 27, 2016 at 2:55 PM, Teresa Johnson <tejohnson at google.com> wrote: > > > On Tue, Sep 27, 2016, 2:38 PM Carsten Mattner <carstenmattner at gmail.com> > wrote: > >> On

...there a configuration in the CI matrix that builds all > of LLVM with ThinLTO so that I can be reasonably sure > any error is most likely local to my environment or > because of operator (silly me) faults? > > $ svn info > URL: http://llvm.org/svn/llvm-project/llvm/branches/release_39 <http://llvm.org/svn/llvm-project/llvm/branches/release_39> > Relative URL: ^/llvm/branches/release_39 > Repository Root: http://llvm.org/svn/llvm-project <http://llvm.org/svn/llvm-project> > Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 > Revision: 290054 > Node...

...You need to have Gold installed, but that is the same requirement as for LTO I believe. > Then if you’re using 3.9 as a host compiler, it should “just work”. $ c++ -v gcc version 6.2.1 20160830 (GCC) $ ld.gold --version GNU gold (GNU Binutils 2.27) 1.12 $ clang -v clang version 3.9.0 (branches/release_39 279763)

...there a configuration in the CI matrix that builds all > of LLVM with ThinLTO so that I can be reasonably sure > any error is most likely local to my environment or > because of operator (silly me) faults? > > $ svn info > URL: http://llvm.org/svn/llvm-project/llvm/branches/release_39 > Relative URL: ^/llvm/branches/release_39 > Repository Root: http://llvm.org/svn/llvm-project > Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 > Revision: 290054 > Node Kind: directory > Schedule: normal > Last Changed Author: tstellar > Last Changed Rev: 288847 >...

...of clang+llvm-3.8.0-x86_64-apple-darwin compilation will be reduced sufficiently: binary 28569 and object 36952 accordingly. Looks like all protocols from UIKit.h is placed into binary/object even it's not used there. I got 3.9.0 from public git (branch release_39 of clang git repository) and found that all protocols interpret as definition (isThisDeclarationADefinition), and in CGObjCGNU.cpp it's placed into object file whenever it's used or not. With the same open source compiler and -fobjc-runtime=ios protocols are not putt...

On Tue, Oct 4, 2016 at 10:15 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Oct 4, 2016 at 2:22 AM, Xinliang David Li <xinliangli at gmail.com> > wrote: > > For clang build, cmake flags: > > > > -DCMAKE_EXE_LINKER_FLAGS=-fuse-ld=gold \ > > -DCMAKE_MODULE_LINKER_FLAGS=-fuse-ld=gold \ > >

...te: > > I can't reproduce the failure. I am building with a clang built > Release from recent source as my stage-1 bootstrap compiler: > clang version 4.0.0 (trunk 282322) (llvm/trunk 282341) The clang I use was built from the 3.9 release branch: clang version 3.9.1 (branches/release_39 281767) Is that too old for it to build itself with ThinLTO? > I am configuring the stage-2 bootstrap compiler with the following > command, which largely is copied from your earlier email with your > cmake command (changes noted below): > > lto=Thin > type=Release > cf...

...to LLVM 5.0.1, the default for 3.9.0 is true [3], and setting it to false wasn't necessary in the latter version. [1] https://nautilus.bjornweb.nl/files/polly501-cfg-simplifycfg-sink-common.pdf [2] https://nautilus.bjornweb.nl/files/polly390-cfg.pdf [3] https://github.com/llvm-mirror/llvm/blob/release_39/lib/Transforms/Utils/SimplifyCFG.cpp#L71 -- Kind regards, Björn Ruytenberg https://bjornweb.nl On 09/03/2018 09:18, Johannes Doerfert wrote: > Hi Björn, > > try to add this: > > -mllvm -simplifycfg-sink-common=false > > Cheers, > Johannes > > On 03/08, B...

...tor (silly me) faults? > There is an lld based ThinLTO buildbot. I've been really remiss in not setting up a gold based ThinLTO bot...note to self to get that done asap! But the existing lld will be head not 3.9. > > $ svn info > URL: http://llvm.org/svn/llvm-project/llvm/branches/release_39 > Relative URL: ^/llvm/branches/release_39 > Repository Root: http://llvm.org/svn/llvm-project > Repository UUID: 91177308-0d34-0410-b5e6-96231b3b80d8 > Revision: 290054 > Node Kind: directory > Schedule: normal > Last Changed Author: tstellar > Last Changed Rev: 288847 >...

I'm compiling a release note for LLD, and I'd like to get you guy's input about the status of the following subsystems. - Current MIPS support - Current AArch64 support - LTO I think AArch64 and LTO are added after the last release, so everything we've made so far should be in the next release note. MIPS's situation is different though. Rui -------------- next part

Hi Martin, On Fri, 3 Aug 2018 at 14:10, Martin J. O'Riordan <MartinO at theheart.ie> wrote: > $ git branch --list > * master > martino By default "git branch" only lists local branches. "git branch -a" will list all of them, including (for me) "remotes/origin/release_70". If you just type "git checkout release_70" git will