Displaying 3 results from an estimated 3 matches for "64vnua".
2008 May 13
1
[LLVMdev] Preferring to use GCC instead of LLVM
...tion. Logic not a strong point in
> your part of the world?
My point was that LLVM alone by itself is incapable of
producing a ready-to-execute .EXE or .DLL, and this fact is
indisputable and agreed by all.
>> Also, "gas" is not available on Windoze.
> http://tinyurl.com/64vnua
Ah you've sent me to a Bart Simpson page. My 2 young kids
watch the Simpsons. I don't.
> And see where the other people in the other thread tell
> you to just redistribute the assembler and linker as part
> of your god-damned project! Are you really this thick?
It is true...
2008 May 13
0
[LLVMdev] LLVM as a DLL
...quot; is required, then LLVM
> is an incomplete back-end solution.
Just like the GCC you were holding up as an example of a complete
back-end solution. Logic not a strong point in your part of the world?
> Also, "gas" is not
> available on Windoze.
http://tinyurl.com/64vnua
> As for NASM, NASM outputs unfinished object files that
> cannot be executed. To translate the object files into
> executable programs, a separate linker program must be used,
> and such a linker program is not normally
> available/installed on customer's computers runnin...
2008 May 13
7
[LLVMdev] LLVM as a DLL
Michael T. Richter wrote:
> Apparently the APIs in the LLVM docs missed your
> attention. They're sneaky that way because, you know,
> they just form the bulk of available documentation.
I began my original message saying that I was providing
"constructive criticism". That means I want to HELP if I
can. Your sarcastic attitude is unprofessional.
> The