search for: release_40

...rom version. > ------------------------------------------------------------------------ > > It should be similar for cfe and the others. > > The current git mirror branch for llvm seems to only have one commit, > and that's one I just made: > > $ git log --oneline origin/release_40 > 817cc1a7301 Merging r291863: > ------------------------------------------------------------------------ > r291863 | chapuni | 2017-01-12 16:17:15 -0800 (Thu, 12 Jan 2017) | 1 > line > > Note that it doesn't have any parent! > > On Fri, Jan 13, 2017 at 9:23 AM, Hans Wen...

Hans, Am 06.03.2017 um 23:25 schrieb Hans Wennborg: > The mailing list thread you linked to talkes about > "multi-configuration generators", such as MSBuild. Have you tried > building with ninja (https://ninja-build.org/) instead? I now tried the ninja build, and that was successful, so I have a workaround. I still would like to know whether I made a mistake with the

On Wed, Mar 8, 2017 at 10:34 AM, Stephan Mühlstrasser <stephan.muehlstrasser at web.de> wrote: > Hans, > > Am 06.03.2017 um 23:25 schrieb Hans Wennborg: >> >> The mailing list thread you linked to talkes about >> "multi-configuration generators", such as MSBuild. Have you tried >> building with ninja (https://ninja-build.org/) instead? > >

> I don't think you made a mistake, I suppose something in the cmake > config is broken. Hi Hans, I can still see the MSVS install error as below with latest LLVM code. Is there any word around can let me install the LLVM through MSVS successfully? CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:37 (file): file INSTALL cannot find

...Total 562 (delta 462), reused 2 (delta 0) Receiving objects: 100% (562/562), 927.00 KiB | 1.29 MiB/s, done. Resolving deltas: 100% (462/462), completed with 240 local objects. >From http://llvm.org/git/llvm 233ecbde652..16c5e12d3a5 master -> origin/master * [new branch] release_40 -> origin/release_40 On Fri, Jan 13, 2017 at 5:49 AM, Nicolai Hähnle <nhaehnle at gmail.com> wrote: > I don't see the release branch in the Git mirror at > http://llvm.org/git/llvm.git yet. Is that going to appear soon? > > Thanks, > Nicolai > > > On 13.01.201...

Hi, I'm trying to do a build and install on Windows 10 with Visual Studio 2015 Community Edition for the X86 and ARM targets, from the current release_40 branch. While compilation completes without error, the INSTALL target fails with the following error: 54> CMake Error at projects/compiler-rt/lib/builtins/cmake_install.cmake:34 (file): 54> file INSTALL cannot find 54> "E:/Users/stm/Documents/GIT/llvm-build-4.0/$(Configuration...

...nd the example program below with gcc 6.3.1 and the result is the same) clang set to default compiler by setting the following environment variables: CC=/usr/bin/clang CXX=/usr/bin/clang++ Commands used to build LLVM: git clone https://github.com/llvm-mirror/llvm.git git checkout release_40 cd llvm mkdir build cd build cmake .. -DLLVM_BUILD_LLVM_DYLIB:BOOL=ON -DLLVM_ENABLE_RTTI:BOOL=ON -DLLVM_ENABLE_EH:BOOL=ON -DLLVM_USE_SANITIZER:STRING=Address -DLLVM_PARALLEL_COMPILE_JOBS:STRING=8 -DLLVM_ENABLE_ASSERTIONS:BOOL=ON cmake --build . -- -j 8 sudo cmake --build . -...

...set to default compiler by setting the following >> environment variables: >> >> CC=/usr/bin/clang >> CXX=/usr/bin/clang++ >> >> Commands used to build LLVM: >> >> git clone https://github.com/llvm-mirror/llvm.git >> git checkout release_40 >> cd llvm >> mkdir build >> cd build >> cmake .. -DLLVM_BUILD_LLVM_DYLIB:BOOL=ON -DLLVM_ENABLE_RTTI:BOOL=ON >> -DLLVM_ENABLE_EH:BOOL=ON -DLLVM_USE_SANITIZER:STRING=Address >> -DLLVM_PARALLEL_COMPILE_JOBS:STRING=8 -DLLVM_ENABLE_ASSERTIONS:BOOL=ON...

...nment variables: >>>> >>>> CC=/usr/bin/clang >>>> CXX=/usr/bin/clang++ >>>> >>>> Commands used to build LLVM: >>>> >>>> git clone https://github.com/llvm-mirror/llvm.git >>>> git checkout release_40 >>>> cd llvm >>>> mkdir build >>>> cd build >>>> cmake .. -DLLVM_BUILD_LLVM_DYLIB:BOOL=ON >>>> -DLLVM_ENABLE_RTTI:BOOL=ON -DLLVM_ENABLE_EH:BOOL=ON >>>> -DLLVM_USE_SANITIZER:STRING=Address -DLLVM_PARALLEL_COMPILE...

...t; CC=/usr/bin/clang >>>>>> CXX=/usr/bin/clang++ >>>>>> >>>>>> Commands used to build LLVM: >>>>>> >>>>>> git clone https://github.com/llvm-mirror/llvm.git >>>>>> git checkout release_40 >>>>>> cd llvm >>>>>> mkdir build >>>>>> cd build >>>>>> cmake .. -DLLVM_BUILD_LLVM_DYLIB:BOOL=ON >>>>>> -DLLVM_ENABLE_RTTI:BOOL=ON -DLLVM_ENABLE_EH:BOOL=ON >>>>>> -DLLVM_USE_...

...ild\lib\Support\LLVMSupport.vcxproj] ... LINK : fatal error LNK1104: cannot open file '..\..\..\lib\Debug\benchmark.lib' [D:\projects\fun\jit_tests\llvm40\llvm40-build\utils\benchmark\src\benchmark_main.vcxproj] i also tried to build LLVM 4 and 6 on a clean cloned version git checkout -b release_40 git checkout -b release_60 producing the very same warnings/errors and the build breaks in the end i've got 1 lib and 2 dlls - not what i've expected :) any ideas?

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 everyone, It has begun: the release branch was recently created from trunk at r291814 and the trunk version was subsequently incremented to 5.0.0 (as per the new versioning scheme [1]). Release blockers are tracked by http://llvm.org/PR31622 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help me out in staying on top of the

Hi, I wanted to know if it was possible to force ARM backend to compile a function in ARM while the rest is in Thumb mode. I tried the attributes which is used in GCC but it doesn't work. Here is what I tried: https://pastebin.com/jCr5LPUY Thanks in advance, Uvekilledkenny -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi Rui, The motivation would be primarily that LLVM/Clang/LLD are community projects such that if I or someone in the community added support for e.g. symbol aliases, then it could be reviewed and potentially merged. ld64 on the other hand does not have a community process for patch submission and code review that I am aware of so its unlikely that if someone from the community came up with a

On Tue, Jun 6, 2017 at 11:14 PM, Michael Clark via llvm-dev < llvm-dev at lists.llvm.org> wrote: > OK. I see that the Mach-O linker is not even built when LLD is enabled in > Release_40, only the PE/COFF and ELF linkers are built. > > From looking at reviews it appears that Clang was able to be linked with > LLD on Darwin about 2 years ago, so Mach-O support seems to have regressed. > Only a few changes have been made to the Mach-O port in the last two years, so I'...

...# %entry pushl %ebp movl %esp, %ebp #APP named_label_1: jne named_label_1 #NO_APP popl %ebp retl .Lfunc_end1: .size bar, .Lfunc_end1-bar This is with clang 4.0.0 from the release_40 branch. I have no idea when the %= support was added. -Dimitry > On 05 Feb 2017, at 10:50, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I think we may already support it. At least that's the implication from the post-commit thread of r288093, in particular...

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

from https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html Under certain circumstances, GCC may duplicate (or remove duplicates of) > your assembly code when optimizing. This can lead to unexpected duplicate > symbol errors during compilation if your asm code defines symbols or > labels. Using ‘%=’ (see AssemblerTemplate) may help resolve this problem. ‘%=’ > Outputs a number that is

Hello testers, 4.0.0-rc3 was just tagged from the branch at r296762. This is a release candidate in the real sense: if no major issues show up with this one, it is the version that will be released. Please let me know if you find any issues, including in release notes or documentation, which will be on the pre-release web site later today. Please build, test, and upload binaries to the sftp