search for: macosx10.9

W dniu 2019-04-04 o 09:18, Tim Northover pisze: > On Wed, 3 Apr 2019 at 19:05, Audiovisart via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Does LLVM 8 work in macOS 10.9.5? > It should do. The released binaries appear to have been compiled so > they can run on that version, and Apple Clang 6.0 (from the newest > Xcode that runs on 10.9) meets the build

On Jun 12, 2014, at 4:37 PM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > On 6/12/14, 3:07 PM, Joseph wrote: >> Hi Dan, >> >> >> So now that the includes are being found building the tutorial results in 74 warnings and 20 errors. Heres a couple examples: >> >> In file included from

Hi, I’ve come back and updated my llvm toolset with modern code (my branch was about 1-2 years old) and now the llvm IR files produced by my front end no longer compile with llc. Here is a sample of llvm ir produced by my front end (it’s a standard version 3.1 build of swift from the swift.org open source website). ; ModuleID = 'main.ll' source_filename = "main.ll" target

That’s useful info, thanks. I think it will be useful for me to understand the connection, why this type of pointer is being emitted now. Do you have any suggestions where i can look to find the platform specific code that is making function pointers go into addrspace? Carl p.s. I am also working on passing the avr target flag to swift, but swift itself had (has?) limitations that make it

Cool. That explains a lot! Sorry if this is a total n00b question, but… how does the datalayout string get overridden? in llvm/lib/Target/AVR/AVRTargetMachine.cpp I can see the code that determines the default datalayout for AVR… static const char *AVRDataLayout = "e-P1-p:16:8-i8:8-i16:8-i32:8-i64:8-f32:8-f64:8-n8-a:8”; However in the LLVM iR below, the target datalayout was present and

Does LLVM 8 work in macOS 10.9.5? -- Mark

Hi Dan, Thank you for your advice on the build/install. On Jun 11, 2014, at 7:06 PM, Dan Liew <dan at su-root.co.uk> wrote: > Well on many Linux distributions LLVM and Clang are installable as > packages (along with the header files) so for something like the > Kaleidoscope tutorial it isn't necessary to build LLVM and Clang from > source. However you are running OSX

Hi, I got the latest LLVM code from git repo, and tried to compile that on my OSX 10.9.4 machine. But I got the error at "make" step: "Makefile:151: /Makefile.rules: No such file or directory" Below is the output of "configure" & "make". Any idea what is wrong? Thanks. $ ./configure --enable-targets=mips checking for clang... clang checking