search for: darwinvers

...=%p/lib/llvm-gcc-4.2 --mandir=%p/share/man --infodir=%p/share/info --with-gmp=%p --with-libiconv-prefix=/usr --with-system-zlib << PatchScript: << #!/bin/sh -ev cd ../llvm-gcc-4.2-%r patch -p1 < %a/%n.patch << CompileScript: << #!/bin/bash -ev ulimit -s `ulimit -s` darwinvers=`uname -r|cut -f1 -d.` mkdir ../llvm_objdir cd ../llvm_objdir if [ `uname -p` = "powerpc" ]; then TRIPLE=powerpc-apple-darwin$darwinvers else TRIPLE=i686-apple-darwin$darwinvers fi ../llvm-2.2-%r/configure %c --build=$TRIPLE --target=$TRIPLE --host=$TRIPLE --enable-optimized -...

...X86SSELevel SSE2 llvm::X86Subtarget::X86SSEEnum X863DNowLevel -842150451 llvm::X86Subtarget::X863DNowEnum HasX86_64 true bool DarwinVers 0 unsigned char stackAlignment 8 unsigned int MaxInlineSizeThreshold 128 unsigned int Is64Bit true bool...

On Feb 12, 2008, at 5:26 PM, Chuck Rose III wrote: > Hola LLVMers, > > I’m debugging through some strangeness that I’m seeing on X64 on > windows with LLVM2.2. I had to change the code so that it would > engage the x64 target machine on windows builds, but I’ve otherwise > left LLVM 2.2 alone. The basic idea is that I’ve got a function bar > which is compiled by

Hola LLVMers, I'm debugging through some strangeness that I'm seeing on X64 on windows with LLVM2.2. I had to change the code so that it would engage the x64 target machine on windows builds, but I've otherwise left LLVM 2.2 alone. The basic idea is that I've got a function bar which is compiled by VStudio and I'm creating another function foo via LLVM JIT which is going