similar to: [LLVMdev] Sparc assembly syntax

On Jul 31, 2008, at 9:57 AM, Dale Johannesen wrote: > > On Jul 31, 2008, at 4:52 AMPDT, Richard Pennington wrote: > >> Any code that I generate for the Sparc fails at assembly time using a >> gas assembler built for the Sparc. >> >> I get code like the following from the code generator: >> >> save -96, %o6, %o6 >> >> and get a syntax

On Jul 31, 2008, at 4:52 AMPDT, Richard Pennington wrote: > Any code that I generate for the Sparc fails at assembly time using a > gas assembler built for the Sparc. > > I get code like the following from the code generator: > > save -96, %o6, %o6 > > and get a syntax error on the save instruction. > > I think sparc syntax should be: > > main: >

Chris Lattner wrote: > This is probably a difference between the sun and GNU assemblers. > There is no current sparc maintainer, so feel free to change it if one > way works better for you. Hi Chris, Here's the fix: Index: SparcRegisterInfo.cpp =================================================================== --- SparcRegisterInfo.cpp (revision 700) +++

Hello. I have been trying to check, how llvm works on Solaris recently. First I have tested lli, whitch seems to execute the bytecode generated on Linux without any problems. However, llc has failed to generate valid SPARC assembler code even on the helloworld example. Here is the generated code: sakharov at trillian:~$ cat ./test.s .text .align 16 .globl main

Hello everyone, I am running an Enterprise 250 with Dual UltraSparc II's and 2 Gb ram running Aurora Sparc Linux 2.0 (2.6.13 kernel for Aurora is based on Fedora Core 3). GCC version 3.4.2. I built llvm-2.0 (the svn version) by just typing "./configure;make". I then downloaded clang from the svn repository (revision 40382) and changed to it's directory under

On Tue, 24 Jul 2007 wilsonk at cpsc.ucalgary.ca wrote: Hi Kelly, Sorry for the delay, I'm way behind in email :( > I built llvm-2.0 (the svn version) by just typing "./configure;make". I > then downloaded clang from the svn repository (revision 40382) and changed > to it's directory under .../llvm/tools/clang. I did a "make" without > incident for clang,

Hello. I have a very simple code like this: int sum(int i, int j) { int k; k = i + j; } #ifdef LINUX #include <stdio.h> #include <stdlib.h> int main () { int k; k = sum(3,4); return k; } #endif If I emit this to SPARC assembly mnemonics through LLVM, it is shown as follows

OK, so the next thing I found in Sparc world is that sparc-elf-as doesn't understand .bss as a directive for some reason. I modified the Sparc code generator to output .section ".bss" and that works just fine. My (temporary) solution is a hack, however: ================================================================== --- SparcAsmPrinter.cpp (revision 720) +++

Hi, :If I compile this file with debugging enabled (clang/LLVM TOT) int main() { } I get the error Error: inconsistent uses of .cfi_sections From the 2.27 binutils assemblers. It seems that 2.27 doesn't like the .cfi_sections .debug_frame directive following previous .cfi directives. The assemblers seem to be happy if the .cfi_sections directive precedes any other .cfi directive. Is

On Sat, 29 Apr 2006, Jeff Cohen wrote: > We know. Someone offered to do the Intel version, but did little more than a > huge cut and paste of the AT&T version and then lost interest. No one else > has had the time or inclination to finish the (barely begun) job. Patches > accepted :) Actually, that's not true. The LLVM X86 backend started out emitting intel mode for

Thanks, Renato. I'm actually porting a project which is based on GAS to iOS platform. I'll report my result. Best regards! ashi On Feb 13, 2013, at 6:20 PM, Renato Golin <renato.golin at linaro.org> wrote: > I don't think there is such a document... > > There isn't a 1:1 compatibility assurance with any syntax, including the UAL and GAS, but there is good

We know. Someone offered to do the Intel version, but did little more than a huge cut and paste of the AT&T version and then lost interest. No one else has had the time or inclination to finish the (barely begun) job. Patches accepted :) Ralph Corderoy wrote: > Hi, > > >> It's a long way towards it: >> >> # AT&T. # Intel.

Hi, It doesn't compile with yasm, or nasm (reports invalid combination of opcode and operands), and mov _x,EAX is meaningless as _x is just a label (an numeric constant that happens to be an address), so it would have to be dereferenced to get to the memory at that address, otherwise it's like saying mov 0x12341234, EAX Now, my asm skills are not that great, so I'm prepared to be

Hi,all. Since the recent clang(3.2) has an integrated assembler for ARM, but I can't find document about this assembler's syntax, such assembler's directive, pseudo-instruction, (I assumed it follows the ARM Unified Assembly Language in instructions), where can I get such information? Thanks! ashi

I don't think there is such a document... There isn't a 1:1 compatibility assurance with any syntax, including the UAL and GAS, but there is good compatibility with most of them, focusing more on GAS than any other, though recent changes are making it more in sync with the UAL (as is happening on GAS, too). I think the recommendation is to try it on, throw code that works on other (OSS)

On 09/27/2015 06:41 PM, Vasileios Kalintiris wrote: > Hi Richard, > > Clang doesn't have support for MIPS I. The trap-on-condition instructions were added in MIPS II and they should work fine. This is why it works with ".set mips32r2". > > Which version of the ISA did you specify when you used the integrated assembler? > > Thanks, > Vasileios > > Hi

I'm not entirely sure what caused this, but the following code, which used to behave as expected, is now broken: ---- lolwut.c ---------------------------- void lolwut(void) { __asm __volatile ( "ldr r1, =1f \n" ".ltorg \n" "1: \n\t" : : : "r0", "r1" ); } ------------------------------------------- ~/clang

Hi,all, I find clang's integrated-as changes fast, My code which can't be compiled by llvm3.1 tool-chain can be compiled by llvm3.2 tool-chain now. However, there are still existing link-errors. My develop environment is: Apple LLVM version 4.2 (clang-425.0.24) (based on LLVM 3.2svn) Target: x86_64-apple-darwin12.2.1 Thread model: posix the code is attached, I get this error (there is no

Some distributions default to PIE for their compilers, which on sparc is passed on to the assembler. Since the behaviour of %hi/%lo changes under PIC to become GOT offsets, the current assembly files need adapting to not try to use a GOT offset as an absolute address. --- usr/include/arch/sparc/machine/asm.h | 15 +++++++++++++-- usr/include/arch/sparc64/machine/asm.h | 1 +

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