similar to: [LLVMdev] Debugger support

On Mon, 12 May 2008, Lokesh Kumar wrote: > I am just curious to know when will the llvm-db be released. I hope I > am posting in the right forum. In the latest release 2.2, the llvm-db > binary doesn't appear to load the symbol table or debug the bytecode. > It spits out a message saying that this feature is still not > implemented. There is no current plan (that I know of) to

I made some researches how llvm, possibly with other tools, can be a full backend for compiler writers (with the final result being an executable file or dynamic linked library). Here are the results: A. Assemblers When I saw that the I86 target for llvm with the Intel syntax targets MASM (I tested with the MASM version from http://www.masm32.com/ ), it was a bad surprise for me. This is

Hey, I've been trying this for a couple days now, finding different assemblers and trying different options but I can't figure it out.. I must be missing something very obvious. I got a simple "hello world" 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

"Razvan Aciu" <admin at kam.ro> writes: [snip] > The problem is with the gcc and binutils licence. This is GPL and [snip] I agree with Owen Anderson on this one (altough IANAL, etc). [snip] > In that respect, if someone can adapt the MASM templates to produce > NASM directives (it is the only thing that needs to be changed), these > updates will be more than

> There's also then entire GNU toolchain, through MinGW and/or Cygwin. Which works perfectly right now without any extra tweaking :) -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

Van Dijck, Tom wrote: > Hey, > > I've been trying this for a couple days now, finding different assemblers and trying different options but I can't figure it out.. > I must be missing something very obvious. > > I got a simple "hello world" app in llvm, making the .bc file using 'llvm-as test.llvm -o=test.bc' works fine. > then I can use llvm-ld to

Yes, you are right. During my testings, I tried the llvm produced .S files with the gcc frontend and it compiled and linked them to the final executable. The problem is with the gcc and binutils licence. This is GPL and while this is ok for open source or for academic purposes, it can't be used on commercial projects. In fact one of the strong points of llvm (and clang) is its BSD like

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

Hello > 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. 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

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 >

On Jan 28, 2010, at 11:51 AM, Dustin 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

> > The more important question is: why would you want to do that? What > problem are you trying to solve? As weird as it sounds, I'm looking for multiplatform assembly languages. I want to learn assembly, but I want my knowledge and code to carry over no matter which operating system I'm using. I regularly use Windows, Mac, and Linux, and I don't want to have to rewrite my

Thanks for your replies. This is indeed a helpful mailing list. I made some more researches about the licensing issue and this is what I discovered: - from FSF it seems that packaging together a GPL application and a commercial one it is a corner case of licensing. Here is what they say: http://www.fsf.org/licensing/licenses/gpl-faq.html#MereAggregation

Here's the new MASM backend. It has the following files :- lib/Target/X86/X86AsmPrinter.h lib/Target/X86/X86AsmPrinter.cpp lib/Target/X86/X86MASMPrinter.h lib/Target/X86/X86MASMPrinter.cpp lib/Target/X86/X86.td lib/Target/X86/X86InstrInfo.td lib/Target/X86/makefile Makefile.rules win32/x86/x86.vcproj

Hi LLVM'ers, has anyone read the license details for MASM32 and understood how these fit in with Open Source projects, especially GPL? - As far as I can see - no one is allowed to license projects under GPL or at worst other OS licenses nor the deritives of the project, if you're using MASM32. Are the MASM backend compatible with the MS version of MASM or other not so license

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

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.html>

Hi, There maybe licencing problems with ML/MASM, we need to get someone to check this out if we are going to support them. NASM and YASM were suggested. Aaron

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

On Mon, 1 May 2006, Jeff Cohen wrote: > Chris Lattner wrote: >> On Mon, 1 May 2006, Ralph Corderoy wrote: >>> NASM might be the nicer target since it's GNU LGPL and runs on multiple >>> OS. Its home page is broken at the moment, but the manual pages work. >>> >>> http://nasm.sourceforge.net/doc/html/nasmdoc0.html >> >> That's