search for: release_60

...ll -- by definition -- not touch the other directories, such a conflict can only happen if you have merges between upstream-svn release branches in your history. E.g., if, in your fork of clang.git, you started working from the release_50 branch, then (potentially after a bunch of work), merged the release_60 branch. In your clang fork, you of course had to resolve any conflicts in clang, but would NOT have resolved conflicts between release_50 and release_60 in "llvm" or other subprojects. The tool can't necessarily know what to do here either. Now, in that case, it's pretty likely t...

...+fxsr,+mmx,+sse,+sse2,+x87" "unsafe-fp-math"="false" "use-soft-float"="false" } !llvm.module.flags = !{!0} !llvm.ident = !{!1} !0 = !{i32 1, !"wchar_size", i32 4} !1 = !{!"clang version 6.0.1-svn334776-1~exp1~20190309042703.125 (branches/release_60)"} Could you tell me why I don't see a and b parameters for the sum function? Thanks Alberto -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20191208/0d499d24/attachment.html>

...e top of the file. > > Argh, I have missed that header. Adding <cstdlib> sounds like the right solution, can you submit a patch or directly commit to SVN if it works for you? I added <cstdlib> to api.cpp, interface.cpp and rtl.cpp, in r322869. Hans, could you please merge it to release_60, or shall I do it? -Dimitry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 223 bytes Desc: Message signed with OpenPGP URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180118/b401e704/attachmen...

...e. >> >> Argh, I have missed that header. Adding <cstdlib> sounds like the right solution, can you submit a patch or directly commit to SVN if it works for you? > > I added <cstdlib> to api.cpp, interface.cpp and rtl.cpp, in r322869. Hans, could you please merge it to release_60, or shall I do it? Go ahead if you're set up, otherwise let me know and I'll do it.

...ld P == not Q. However, I don't think that current DFAPacketizer can represent these situations. References: [1] Code Generation Schemas for Modulo Scheduled DO-loops and WHILE-loops http://www.hpl.hp.com/techreports/92/HPL-92-47.pdf?jumpid=reg_R1002_USEN Code: The sample patch for origin/release_60 [2], which doesn't use DFAPacketizer, can generate executable files from sample-code.c for both AArch64 and x86_64. [AArch64]% clang -O2 -mcpu=thunderx2t99 -mllvm -enable-pipeliner -mllvm -pipeliner-max=100 sample-code.c [x86_64] % clang -O2 -march=sandybridge -mllvm -enable-pipeliner...

....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?

.../ copy back the data dc.download(c); } Recently, I open sourced PACXX on github [3] under the same license LLVM is currently using. Since my PhD is now in its final stage I wanted to ask if there is interest in having such an SPMD programming model upstreamed. PACXX is currently on par with release_60 and only requires minor modifications to Clang, e.g., a command line switch, C++ attributes, some diagnostics and metadata generation during code gen. The PACXX-RT can be integrated into the LLVM build system and may remain a standalone project. (BTW, may I ask to add PACXX to the LLVM projects?)....

Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: > On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers > <release-testers at lists.llvm.org> wrote: >> Start your engines; 6.0.0-rc1 was just tagged. >> >> I know there are still open blockers and it's early in the process in >> a way, but I'd like to find out where we are. Please run the

...PACXX: > > ... > > Recently, I open sourced PACXX on github [3] under the same license LLVM is currently using. > Since my PhD is now in its final stage I wanted to ask if there is interest in having such an SPMD programming model upstreamed. > PACXX is currently on par with release_60 and only requires minor modifications to Clang, e.g., a command line switch, C++ attributes, some diagnostics and metadata generation during code gen. > The PACXX-RT can be integrated into the LLVM build system and may remain a standalone project. (BTW, may I ask to add PACXX to the LLVM projec...

...gt;>> Argh, I have missed that header. Adding <cstdlib> sounds like the right solution, can you submit a patch or directly commit to SVN if it works for you? >> >> I added <cstdlib> to api.cpp, interface.cpp and rtl.cpp, in r322869. Hans, could you please merge it to release_60, or shall I do it? > > Go ahead if you're set up, otherwise let me know and I'll do it. Done in r323037. I have also taken the liberty of merging r322875 and r322879, in which I added a '-no-libcxxabi' option to the test-release.sh script. -Dimitry -------------- next par...

...t;> ... >> >> Recently, I open sourced PACXX on github [3] under the same license LLVM is currently using. >> Since my PhD is now in its final stage I wanted to ask if there is interest in having such an SPMD programming model upstreamed. >> PACXX is currently on par with release_60 and only requires minor modifications to Clang, e.g., a command line switch, C++ attributes, some diagnostics and metadata generation during code gen. >> The PACXX-RT can be integrated into the LLVM build system and may remain a standalone project. (BTW, may I ask to add PACXX to the LLVM pro...

...d specific svn commands for starting with a LLVM 6.0 release and later upgrading to LLVM 7.0 below. svnadmin create repos svn mkdir file://`pwd`/repos/llvm svn mkdir file://`pwd`/repos/llvm/trunk svn mkdir file://`pwd`/repos/llvm/branches svn export http://llvm.org/svn/llvm-project/llvm/branches/release_60 llvm_60 svn import llvm_60 file://`pwd`/repos/llvm/trunk/llvm_60 svn copy trunk/llvm_60 file://`pwd`/repos/llvm/trunk/myproj60 //Make project changes to trunk/myproj60. //When next llvm release is available (say llvm 7.0) svn diff file://`pwd`/repos/llvm/trunk/llvm_60 file://`pwd`/repos/ll...

...quot;false" "use-soft-float"="false" } >> >> !llvm.module.flags = !{!0} >> !llvm.ident = !{!1} >> >> !0 = !{i32 1, !"wchar_size", i32 4} >> !1 = !{!"clang version 6.0.1-svn334776-1~exp1~20190309042703.125 >> (branches/release_60)"} >> >> Could you tell me why I don't see a and b parameters for the sum function? >> >> Thanks >> Alberto >> _______________________________________________ >> LLVM Developers mailing list >> llvm-dev at lists.llvm.org >> https://list...

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