similar to: [LLVMdev] Native Assembler for ARM

On Sat, Sep 19, 2009 at 2:37 PM, Wayne Anderson <wanderon at comcast.net>wrote: > I hope I'm not missing something obvious. I'm trying to get a native > binary for ARM from a .s file. If I try to run "as -arch arm > myFile.s" I get an error message indicating that no installed > assembler exists for arm. > > as: assembler

If you want Darwin arm assembler, then you need to register and download the iphone sdk. Evan On Sep 19, 2009, at 11:48 AM, Misha Brukman wrote: > On Sat, Sep 19, 2009 at 2:37 PM, Wayne Anderson > <wanderon at comcast.net> wrote: > I hope I'm not missing something obvious. I'm trying to get a native > binary for ARM from a .s file. If I try to run "as -arch

I am trying to cross compile an assembly file using clang but with " -fno-integrated-as" so that clang does not use its own assembler. Clangs calls the command: /usr/bin/aarch64-linux-gnu-as -o Myfile.o Myfile.s but it fails because of missing *-march=armv8-a+crypto *which is required to build build my source file Myfile.s I am passing "-march=armv8-a+crypto" to clang command

I am trying to build chromium and at this moment, They see some issues with internal one so recommended to use the flag -fno-integrated-as. Here is my exact build command (with -v and --save-temps): $ clang -Igen -I../../include -target aarch64-linux-gnu -march=armv8-a+crypto -fno-integrated-as --sysroot=./debian_jessie_arm64-sysroot -O2 -c MyFile.S -o MyFile.o -v --save-temps clang version

Hi all, I'm currently implementing a linux/ppc target in llvm. The abis between Darwin/ppc and linux/ppc are different and I'm running into problems with vararg calls. Before a variadic method is called, an extra instruction must be executed (which is creqv 6, 6, 6). This instruction is not necessary in Darwin/ppc. I looked into the PowerPC target implementation and the code generation

On 30 Jul 2014, at 21:29, Ulrich Weigand wrote: > The ELFv1 ABI is used on 64-bit big-endian Linux and AIX. There's one small difference between the two: with the 64 bit ELFv1/ SVR4 ABI, tail padding for structs passed by value is only performed in case the struct is larger than 8 bytes, while for AIX 64 bit it's always done. As an aside, on Darwin/ppc64 it's done if the

I was successful in compiling asterisk in raspbien except for the following error If I enable the gsm codec. It appears there is something in the Makefile n this directory that needs to be changed. Probably involving optimization. Not sure why it does not recognize the processor since it is one that is mentioned in the Makefile.? Any help would be appreciated. make[2]: Entering directory

I am having an issue with MCJIT on the ppc64 machine architecture. The symptom is that for a particular IR function the target machine won't emit neither an object nor an assembly file and subsequent calling the pointer to function results in a segfault. My application generates on the fly several functions with the builder and executes them with the MCJIT engine. I came across this

On Fri, 12 Jan 2007, Nicolas Geoffray wrote: > I'm currently implementing a linux/ppc target in llvm. The abis between cool > Darwin/ppc and linux/ppc are different and I'm running into problems > with vararg calls. ok > Before a variadic method is called, an extra instruction must be > executed (which is creqv 6, 6, 6). This instruction is not necessary in >

This fixes a segmentation fault in the system call's error handling path with dynamically-linked binaries on PowerPC64 little endian. The system call stub wasn't loading up r2 with the appropriate TOC value in its global entry point. The r2 setup code comes from the FUNC_START macro in gcc [1] and an equivalent one can also be found in the LOCALENTRY macro in glibc [2]. On the ELFv2 ABI

Hi, For the last 3 days or so trunk fails to compile on PPC64/Linux with: [16257s] /tmp/DAGCombiner-N3D9ir.s: Assembler messages: [16257s] /tmp/DAGCombiner-N3D9ir.s:12394: Error: operand out of range (0x00000000000192b4 is not between 0xffffffffffff8000 and 0x0000000000007ffc) [16257s] clang: error: assembler command failed with exit code 1 (use -v to see invocation) Anyone seeing a similar

On Sat, 28 Apr 2012 13:55:13 -0500 Hal Finkel <hfinkel at anl.gov> wrote: > On Sat, 28 Apr 2012 13:46:02 -0500 > Hal Finkel <hfinkel at anl.gov> wrote: > > > On Sat, 28 Apr 2012 11:19:13 -0500 > > Peter Bergner <bergner at vnet.ibm.com> wrote: > > > > > On Fri, 2012-04-27 at 20:30 -0500, Hal Finkel wrote: > > > > Thanks! Do you

On Sat, 2012-04-28 at 15:51 -0500, Hal Finkel wrote: > > > - There is no support for generating position-independent code on > > > PPC32. (PIC on PPC64 now works well). Nevertheless, I have > > > sometimes run into linking errors when compiling shared libraries > > > with C++ on PPC64. PPC64 is PIC by nature. As for the linking issue, possibly you blew the

On 07/20/2012 10:35 AM, Will Schmidt wrote: > On Fri, 2012-07-20 at 08:36 +0200, Duncan Sands wrote: >> Hi Adhemerval Zanella, the old JIT infrastructure is going away, to be replaced >> by "MC-JIT" (try passing -use-mcjit to lli). It sounds like you are working on >> the old JIT, so I suggest you work instead on getting MC-JIT working on powerpc. > Hi Duncan,

TL;DR: If I'm trying to define new assembler directive syntax to support DWARF v5, it seems like a good idea for all the various assemblers out there in the world to support the same syntax. How would I go about negotiating that syntax with other assembler providers? Is GNU as the only really relevant one? Long version: DWARF v5 introduces a couple of new features in the .debug_line section

When compiling trunk using gcc 4.1.2 on linux/ppc64, I now see a warning that I don't remember seeing previously: llvm[2]: Compiling InlineSpiller.cpp for Release+Asserts build /src/llvm-trunk-dev/include/llvm/ADT/PointerIntPair.h: In member function ‘const PointerTy* llvm::PointerIntPair<PointerTy, IntBits, IntType, PtrTraits>::getAddrOfPointer() const [with PointerTy = void*, unsigned

While the MCJIT doesn't cover all of the features the old JIT had, it has the huge advantage of actually producing working results on ARM and PPC64. The old JIT for non-x86 has bit-rotted a lot, to the point of crashing even for simple examples. I'm proposing to remove the JIT code emitters for the ARM and PPC targets now so it's no longer holding back the development of the MC parts

Hi all, I compiled 64-bit R on an Apple Mac G5 running OS X, but it failed make check. Simon Urbanek suggested I post results to R-devel. > On Nov 6, 2007, at 10:23 PM, Steven McKinney wrote: > > > Hi Simon, > > > > Would you be able to give more guidance on how to compile 64-bit > > libiconv for Tiger, > > You can get the sources from Apple and compile

To pass the MD5 checksum to the assembler, I added a new optional clause to the .file directive: md5 "checksum" where checksum is the 16-byte checksum in hex. It's quoted because the assembler doesn't have a way to parse a 16-byte integer. Also this is the same syntax Reid invented for the CodeView equivalent. To convey the root source filename, I allow the file number on the

From: Heiko Carstens <heiko.carstens@de.ibm.com> vfork support for s390/s390x. Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com> --- diff -purN a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def --- a/usr/klibc/SYSCALLS.def 2006-06-07 09:44:33.000000000 +0200 +++ b/usr/klibc/SYSCALLS.def 2006-06-07 13:01:54.000000000 +0200 @@ -28,7 +28,7 @@ void _exit,exit::_exit(int) ; A