similar to: [LLVMdev] llvm partly ported to windows

Hello (again)! I fixed most of the system and the following projects compile now: * Analysis * AsmParser * Bytecode * CBeckend * Codegen * ExecutionEngine * Support * System * TableGen * Target * Transforms * VMCore I would like to compile at least x86 target as well as Fibonacci example (to test if it really works). In order to do so, I may need some hints: 1) How to generate

On Sat, 4 Nov 2006, Reid Spencer wrote: > On Sun, 2006-11-05 at 00:27 +0300, Anton Korobeynikov wrote: > >>> 2) Is bugpoint project buildable on windows? >> Yes. > > Really? Yep. > When did that happen? Apparently Dec 22, 2005. Some rspencer guy did it: http://llvm.org/bugs/show_bug.cgi?id=351 > Are we now just execing the sub-processes > instead of

LMAO .. I don't even remember the changes I've made .. and less than a year ago. I am getting old. Reid. On Sat, 2006-11-04 at 16:50 -0800, Chris Lattner wrote: > On Sat, 4 Nov 2006, Reid Spencer wrote: > > > On Sun, 2006-11-05 at 00:27 +0300, Anton Korobeynikov wrote: > > > >>> 2) Is bugpoint project buildable on windows? > >> Yes. > > >

On Sun, 2006-11-05 at 00:27 +0300, Anton Korobeynikov wrote: > > 2) Is bugpoint project buildable on windows? > Yes. Really? When did that happen? Are we now just execing the sub-processes instead of forking them? Reid.

my build environment: Win7 x64 VStudio 2017 Community Edition 15.8.4 (latest) CMake 3.12.1 (x86) git 2.19.0 (latest, x64) Python 2.7.2 (x86) x64 Native Tools Command Prompt for VS 2017 directory structure: test     llvm <-- git clone https://github.com/llvm-mirror/llvm, git checkout release_70       tools         clang <-- git clone https://github.com/llvm-mirror/clang, git checkout

> I may be missing something obvious, but what is `vector` defined as here? Can you provide a buildable example? Sorry, I should provide a cross-platform version using vector extension of frontend :) `vector int` is a vector extension on PowerPC, which is enabled if you set target to PowerPC platforms. Example below should be successfully compiled in any platform: typedef float v4sf

I've noticed that some reviews, but not others, show up in Phab with a "buildable" indication in a "Diff Detail" box, just below the summary. Can somebody describe what that's about? Most interesting might be why it's there only sometimes, also what sort of "build" this indication is reporting. Thanks, --paulr

// hoping this is sufficiently on-topic // php-driven, markdown-aware, open source wiki/cms that has some degree of version control, a flexible system for privs/access control, is installable (or buildable) on OS X and has an easy installer for windows ?

Hello! I'm wondering whether compiler-rt is expected to be buildable with MSVC 2013. I am currently getting: Error 49 error LNK2005: _free already defined in asan_malloc_win.obj E:\llvm\crt_build\lib\asan\MSVCRT.lib(MSVCR120.dll) Which seems to be the only issue (aside from ~50 warnings, which I'll happily work on cleaning up). I get this when I build the ALL_BUILD project in the

Reid, > No. It uses Unix specific calls (fork). Until that's resolved, it won't > compile correctly. This was fixed before 1.8 release. Bugpoint nowadays compiles and runs fine on windows. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Apparently this didn't/doesn't build on FreeBSD by default...or is it "doesn't build at all". If it is buildable, what should I do to build it, as without it...see wiki: http://wiki.samba.org/index.php/Samba4/Winbind Cheers, TMS III

I constructed an LLVM 2.7 VS solution with cmake, but it has 66 projects: ALL_BUILD, ".\ALL_BUILD.vcproj" BrainF, "examples\BrainF\BrainF.vcproj" Fibonacci, "examples\Fibonacci\Fibonacci.vcproj" FileCheck, "utils\FileCheck\FileCheck.vcproj" HowToUseJIT,

I am wondering about updating the version of Spam Assassin on my CentOS 5 mail server. The current version, 3.3.1-4.el5 (stock RHEL version), has been 'leaking' recently. I suspect I need some newer match rules to detect some of the newer flavors of spam. I see that in rpmforge's extras repo is version 3.3.2-4.el5.rfx -- is this version worth installing? Are there even newer versions

On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: > Yes it is. > Are you doing a Debug or Release build? > Using ninja? Release build, cmake + MSVC (not using ninja). Perhaps I have it configured stupidly; I have it as an out-of-tree folder, did: E:\llvm\crt_build>cmake -DLLVM_CONFIG_PATH=E:\llvm\2013\Debug\bin -G "Visual Studio 12"

Hi. As per[1], gcc-4.8 is the oldest supported *major* gcc version. But what about minor/patch versions? When https://reviews.llvm.org/D43779 was initially committed, a few[2][3] buildbots failed. As i have now looked into the issue: * but it is *REPRODUCIBLE* with gcc-4.8.4 and gcc-4.9.2 from debian oldstable (Jessie). * it is *NOT* reproducible with gcc-4.8.5 and gcc-4.9.3 from ubuntu 16.04,

Canonicalizing to a masked store intrinsic is possible, but we might have to expand back to the load/shuffle/store sequence for targets that don't support masked store. And then you'd likely have to do the store splitting that I think is being requested for the original pattern anyway. But I'd like to step back to the premise - "LLVM seems to always generate vector instructions

Hi All, I just posted a review with arcanist (which I'm fairly new to) and it included a build status. How it got there is totally opaque to me, but my workflow was: Using git+svn (following the setup in https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-git-svn) make a change, commit with 'git commit', create review with 'air diff'. It would be cool if

Hello, After commit 93af05e03e05d2f85b5a7e20ec3a3a543584d84f we have new warning but only if compiled with GCC: In file included from /path/to/llvm/include/llvm/ExecutionEngine/Orc/ExecutionUtils.h:19:0, from /path/to/llvm/lib/ExecutionEngine/Orc/OrcMCJITReplacement.h:23, from /path/to/llvm/lib/ExecutionEngine/Orc/OrcMCJITReplacement.cpp:9:

Hi All, The landed patch https://reviews.llvm.org/D38481 introduced the usage of CPU_COUNT defined in glibc sched.h header. I failed to find this symbol in sched.h of glibc version 2.5-24, so compilation just fails. /home/dolphin/merge-from-upstream-area/ws/pristine/lib/Support/Threading.cpp: In function 'unsigned int llvm::hardware_concurrency()':

http://llvm.org/bugs/show_bug.cgi?id=21241 ? 2014-10-23 10:18 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>: > On Thu, Oct 23, 2014 at 1:15 PM, Aaron Ballman <aaron at aaronballman.com> wrote: >> On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: >>> Yes it is. >>> Are you doing a Debug or Release build?