similar to: [LLVMdev] how to compile asm output for x86 with Micorsoft's ML

Jim Crafton <jim.crafton at gmail.com> writes: [snip] > I looked around a bit but couldn't find anything. The example on the > llvm site mentions being able to compile to C code, but when I try llc > -march=c test.out > > it errors out with: > error: invalid target 'c'. [snip] > Registered Targets: > x86 - 32-bit X86: Pentium-Pro and above

> By default, the cmake build generates Visual Studio project files for > the X86 target only. Take a look at > > http://www.llvm.org/docs/CMake.html#llvmvars > > for learning how to build other targets. OK thanks, I'll look at that. In the meantime, is it possible to get the assembly generated by llc to work wiht ML? That would probably be the ideal solution. Cheers Jim

On Jan 21, 2010, at 12:54 PM, Jim Crafton wrote: >> By default, the cmake build generates Visual Studio project files for >> the X86 target only. Take a look at >> >> http://www.llvm.org/docs/CMake.html#llvmvars >> >> for learning how to build other targets. > > OK thanks, I'll look at that. > > In the meantime, is it possible to get the

> Nope, llvm's .s output is only compatible with GAS and other at&t syntax > assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is > not production quality for use by a compiler.  This is why visual studio > doesn't go through it.  Long term, we'd like LLVM to be able to write out .o > files directly, if you're interested in adding PECOFF

On Jan 21, 2010, at 2:01 PM, Jim Crafton wrote: >> Nope, llvm's .s output is only compatible with GAS and other at&t >> syntax >> assemblers. It turns out that MASM syntax is highly ambiguous and >> MASM is >> not production quality for use by a compiler. This is why visual >> studio >> doesn't go through it. Long term, we'd like

Did pecoff support means we can linkage llvm generated obj files to msvc's obj files? 2010/1/22, Jim Crafton <jim.crafton at gmail.com>: >> Nope, llvm's .s output is only compatible with GAS and other at&t syntax >> assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is >> not production quality for use by a compiler.  This is why visual

It would be nice to be able to use clang/llvm without GNU toolchain dependencies. Just out of curioisty what does the --x86-asm-syntax=intel actually mean then? Does this not get used? Is this a different syntax than the AT&T variety (forgive me if this is an obvious question)? I tried downloading FASM last night and it seemed handle some of the output, the one thing it didn't like was

> Regarding the pecoff support - FASM comes with complete source and > what appears to be a BSD license. It outputs to pecoff. Assuming the > FASM code is readable and reasonably understandable, could this code Scratch all that, my mistake, it's all assembly. Cheers Jim

Hi Guys Im trying to complile Asterisk on my new dual Xeon 3.0ghz EM64T machine. Im running Debian 3.1, and have installed the 2.6.8-11-em64t-p4-smp kernel (and headers). The system is working fine and is detecting both CPU's (4 actually, with hyperthreading). But when I try to compile Zaptel, Im getting this error: /lib/modules/2.6.8-11-em64t-p4-smp? /build make -C

Hi all, My Ct's box is RH 3.0 SMP kernel EM64T. They are asking if OCFS for SMP (EM64T) is available or not. In following site, we can not see OCFS for SMP (EM64T). http://oss.oracle.com/projects/ocfs/files/RedHat/RHEL3/x86_64/1.0.14-1/ ---------- ocfs-2.4.21-EL-1.0.14-1.ia32e.rpm OCFS driver for kernel version 2.4.21-27.EL and higher (EM64T) ocfs-2.4.21-EL-1.0.14-1.src.rpm OCFS driver

Red Hat is pleased to announce the availability of Update 2 for the Red Hat Enterprise Linux 4 family of products, including: - Red Hat Enterprise Linux AS 4 for x86, AMD64/EM64T, Itanium, POWER, S/390 and zSeries - Red Hat Enterprise Linux ES 4 for x86, AMD64/EM64T, Itanium - Red Hat Enterprise Linux WS 4 for x86, AMD64/EM64T, Itanium - Red Hat Desktop 4 for x86 and AMD64/EM64T Craig

Dear developeRs, I'm trying to build R (2.7.1, on an x86_64 running Linux, but I believe I have observed this on x86 and with earlier versions of R as well) using external BLAS and LAPACK libraries _and_ generating libR.so, libRblas.so and libRlapack.so. Without --enable-BLAS-shlib, configure is able to find and use the external LAPACK library: ./configure \

NO Hi. I'm not sure if this is an R-help or R-devel problem, so I'm starting here in the hope that someone can help (and willing to go to the other list if it's more appropriate). I think I am following all of the instructions in the various manuals, but clearly I am missing something. I have an Intel EM64T Dell with 2 dual-core Xeon processors running Red Hat EL5. I would

While update 3 was released last week, it looks like there are 40 or so packages updated. I dunno about squid, it is listed on http://rhn.redhat.com/errata/rhel4as-errata.html but the changelog is from October 2005 (unless it is an rhel only bug). audit-1.0.12-1.EL4.i386.rpm audit-libs-1.0.12-1.EL4.i386.rpm audit-libs-devel-1.0.12-1.EL4.i386.rpm bootparamd-0.17-21.RHEL4.i386.rpm

Hello, Will "R" work on this 64 bit machine?, Here are the specs. of our linux box: *Red Hat Enterprise Linux WS (v.3 Standard for AMD64 and Intel EM64T) *OS: redhat-release Release: 3WS CPU Arch: ia32e-redhat-linux (4) GenuineIntel Intel(R) Xeon(TM) CPU 3.40GHz 3399 MHZ Arch: EM64T Cache: 1024 KB Vendor: GenuineIntel Memory: 2000 MB Stepping: 1 Family: 15 Swap: 4000

Hi, I'm trying to follow the R-admin instructions for using MKL10 as the external BLAS compiling R-2.6.2 under Linux on a RH EL head node of a cluster. The configure process seems to have problems when it checks for dgemm in the BLAS. I'm using configure as: ./configure CC=icc F77=ifort --with-lapack="$MKL" --with-blas="$MKL" where $MKL is defined as in R-admin

Hi all, I'm trying to build R from subversion with MKL 10.0.2 on Ubuntu. I tried: ./configure --with-blas='-L/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lguide' --with-lapack='/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lmkl_lapack' --enable-R-shlib and got: R is now configured for x86_64-unknown-linux-gnu Source directory: . Installation directory: /usr/local

Hi all, I'm trying to build R from subversion with MKL 10.0.2 on Ubuntu. I tried: ./configure --with-blas='-L/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lguide' --with-lapack='/opt/intel/mkl/10.0.2.018/lib/em64t -lmkl -lmkl_lapack' --enable-R-shlib and got: R is now configured for x86_64-unknown-linux-gnu Source directory: . Installation directory: /usr/local

Hello! I have been successful using SYSLINUX and Etherboot to create a generic "PXE-on-a-disk" package, a floppy image and CD image that support as many Ethernet cards as possible. These have support for all of Etherboot's modules that support real PCI cards: about 25-or-so drivers and 250-or-so cards. I've built Etherboot ZLILO images, one for each driver, set up to boot

I'm looking to install Asterisk on an EM64T Dell 1850. PERC raid 1, 1GB ram, single 3Ghz Xeon. Any red flags or anything I should know? Should I bother installing a 64 bit OS? (gentoo-amd64)? Does asterisk work in 64 bit mode? Should I turn hyper threading off? Etc?