search for: fasm

.../build/test' Making a new site.exp file... XPASS: /home/ssen/llvm/test/FrontendC/2009-08-11- AsmBlocksComplexJumpTarget.c make[1]: Leaving directory `/home/ssen/llvm/build/test' ssen at ssen:~/llvm/build$ /usr/local//llvm/bin/gcc ../test/FrontendC/ 2009-08-11-AsmBlocksComplexJumpTarget.c -fasm-blocks -S -o - | grep 1192 jmp *1192(%eax) Should -fasm-blocks really be supported on non-Darwin targets? Shantonu Sen ssen at apple.com Sent from my Mac Pro

...s there a workaround to avoid these warnings (without turning off -Wunused-label)? Here is a small sample code that exhibits the issue: int main() { __asm__ { MyLabel: sub ebx,8 jg MyLabel } return 0; } Compile with llvm-gcc 4.2 on MacOSX 10.6: llvm-gcc-4.2 -arch i386 -Wunused-label -fasm-blocks -o inlineassembly_llvm inlineassembly.c inlineassembly.c: In function ‘main’: inlineassembly.c:7: warning: label ‘LASM$MyLabel’ defined but not used Compile with gcc 4.2 on MacOSX 10.6: gcc -arch i386 -Wunused-label -fasm-blocks -o inlineassembly inlineassembly.c no warnings Thanks, Alex...

...n Laurence wrote: > On 01/28/2010 11:41 AM, Anton Korobeynikov wrote: >> >> The required efforts equal to ones required to write new assembler. >> "Too weak to be usable" means "it's not possible to represent many >> important constructs with masm/nasm/fasm". > > Wow. It's perhaps too much of a distraction, but I'm curious about > the > details of this. It's probably because it's first mission is to be a > compiler back-end, but the common wisdom is that gas is bare-bones and > masm is featureful. Clearly th...

On 01/28/2010 11:41 AM, Anton Korobeynikov wrote: > > The required efforts equal to ones required to write new assembler. > "Too weak to be usable" means "it's not possible to represent many > important constructs with masm/nasm/fasm". Wow. It's perhaps too much of a distraction, but I'm curious about the details of this. It's probably because it's first mission is to be a compiler back-end, but the common wisdom is that gas is bare-bones and masm is featureful. Clearly that doesn't hold for what...

...ould 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 the string variable. It complained about mov DWORD PTR [ESP], ($_.str) something about "$_.str" wasn't kosher. On Thu, Jan 21, 2010 at 5:56 PM, Chris Lattner <clattner at apple.com> wrot...

...quired to make > intel asm printer to be usable? If it is within weeks, probably I can give > it a try. The required efforts equal to ones required to write new assembler. "Too weak to be usable" means "it's not possible to represent many important constructs with masm/nasm/fasm". -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Thanks for Anton's reply. Does anybody have an idea of roughly how much effort is required to make intel asm printer to be usable? If it is within weeks, probably I can give it a try. Thanks, Bengu On Thu, Jan 28, 2010 at 12:18 AM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > Hello > > > system native assemlber and linker to generate executables. And it >

...gt; Here is a small sample code that exhibits the issue: > > int main() > { > __asm__ > { > MyLabel: > sub ebx,8 > jg MyLabel > } > > return 0; > } > > > Compile with llvm-gcc 4.2 on MacOSX 10.6: > > llvm-gcc-4.2 -arch i386 -Wunused-label -fasm-blocks -o > inlineassembly_llvm inlineassembly.c > inlineassembly.c: In function ‘main’: > inlineassembly.c:7: warning: label ‘LASM$MyLabel’ defined but not used > > Compile with gcc 4.2 on MacOSX 10.6: > > gcc -arch i386 -Wunused-label -fasm-blocks -o inlineassembly > i...

I've tried compiling with tinycc, and assembling with yasm, and fasm even with intel syntax. I'm just wondering what available compilers and assemblers there are without trying every one of them. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090408/b779a781/attachment.ht...

Could you give me some examples of such constructs that are not possible to represent with MASM/NASM/FASM but are able to represent with gas? Thanks, Bengu On Thu, Jan 28, 2010 at 11:41 AM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > Hello > > > Does anybody have an idea of roughly how much effort is required to make > > intel asm printer to be usable? If it is...

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

...gt;> On 01/28/2010 11:41 AM, Anton Korobeynikov wrote: >>> >>> The required efforts equal to ones required to write new assembler. >>> "Too weak to be usable" means "it's not possible to represent many >>> important constructs with masm/nasm/fasm". >> >> Wow. It's perhaps too much of a distraction, but I'm curious about >> the >> details of this. It's probably because it's first mission is to be a >> compiler back-end, but the common wisdom is that gas is bare-bones and >> masm is f...

.../www.tortall.net/projects/yasm/ ) - it is NASM compatible and has a BSD license, much as llvm has. A strong point for YASM is that it is from start built like a library (the same as llvm), so it can be simply integrated in a developer tool. YASM is my personal favorite for llvm integration. 3. FASM ( http://flatassembler.net/ ) - it is an assembler written in assembler, which works on Windows and Linux. It has a liberal license and as a strong point it can produce directly executables or dynamic libraries, without a linker. The major problem with it is that it can only be interfaced hardl...

> 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

...y? Why not just write in C?*And there's only so much assembly you can learn by calling C functions, instead of writing lower level code. I understand that OS's have different conventions for I/O, but what I don't understand is why multiplatform assembly languages like LLVM, NASM, YASM, FASM, and Gas don't give coders an macro or instruction set that gets expanded to the actual, per-OS instructions during assembly. I guess it lowers development efforts to reuse libc rather than add multiplatform I/O assembly macros. Smaller, non-libc dependent binaries don't matter in a world w...

..." app in llvm, making the .bc file using 'llvm-as test.llvm -o=test.bc' works fine. then I can use llvm-ld to make an executable which then runs fine (although not native), and I can use llc to build the .bc file into a .s file. So far I'm all good... But neither masm, yasm, tasm, fasm, gcc, as, or nasm take the .s file. I only found one other post about this where it was mentioned that only 'GAS" can compile it, so I tried this in both Cygwin and Ubuntu, but to no avail. In cygwin I get: $ gcc /cygdrive/d/test.s /cygdrive/d/test.s: Assembler messages: /cygdrive/d/test...

Hello. Is there a way to output native assembly from llvm-ld to FASM? Also when I tried to compile C code generated by llc with TCC, it complained about not having the alloca.h header. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090406/c3243719/attachment.html>

> I've tried compiling with tinycc, and assembling with yasm, and fasm even > with intel syntax. I'm just wondering what available compilers and > assemblers there are without trying every one of them. gas -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

> 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

...ray with unspecified bounds} child process exited abnormally FAIL: /usr/local/src/llvm/test/FrontendC/inline-asm-function.c Failed with exit(1) at line 1 while running: /usr/local/llvm-gcc4.2-2.7-x86_64-linux/bin/llvm-gcc -emit-llvm -w -S /usr/local/src/llvm/test/FrontendC/inline-asm-function.c -fasm-blocks -o - -O | /bin/grep naked child process exited abnormally Running /usr/local/src/llvm/test/FrontendC++/dg.exp ... FAIL: /usr/local/src/llvm/test/FrontendC++/2010-02-17-DbgArtificialArg.cpp Failed with exit(1) at line 1 while running: /usr/local/llvm-gcc4.2-2.7-x86_64-linux/bin/llvm-gcc -e...