Comments on: Xiph needs someone to help with assembly for MSVC! http://blog.hartwork.org/?p=86 Free Software and Music Thu, 02 Sep 2010 01:58:30 +0200 http://wordpress.org/?v=2.8.6 hourly 1 By: Uk Landfill http://blog.hartwork.org/?p=86&cpage=1#comment-60911 Uk Landfill Wed, 25 Mar 2009 20:32:12 +0000 http://blog.hartwork.org/?p=86#comment-60911 why not translate gnu into a bill gates compatible format? why not translate gnu into a bill gates compatible format?

]]> By: gmxtrqd nxdpajkuz http://blog.hartwork.org/?p=86&cpage=1#comment-8261 gmxtrqd nxdpajkuz Thu, 10 Jan 2008 16:07:38 +0000 http://blog.hartwork.org/?p=86#comment-8261 knvpy mqouigr icmoqzspa xmivuctnb uzsgfjvd rnegjbpxh ancxif knvpy mqouigr icmoqzspa xmivuctnb uzsgfjvd rnegjbpxh ancxif

]]> By: berkus http://blog.hartwork.org/?p=86&cpage=1#comment-3684 berkus Tue, 09 Oct 2007 23:34:41 +0000 http://blog.hartwork.org/?p=86#comment-3684 As an other interesting approach you can use Bernstein's qhasm :) http://cr.yp.to/qhasm.html As an other interesting approach you can use Bernstein’s qhasm :)
http://cr.yp.to/qhasm.html

]]> By: Thiago Macieira http://blog.hartwork.org/?p=86&cpage=1#comment-3629 Thiago Macieira Mon, 08 Oct 2007 11:28:43 +0000 http://blog.hartwork.org/?p=86#comment-3629 You can also tell gcc to generate Intel-syntax assembly. And then you can have your inline assembly in your .c files in the Intel style as well. It might be even possible to do that on-the-fly in the inline assembly. You can also tell gcc to generate Intel-syntax assembly. And then you can have your inline assembly in your .c files in the Intel style as well.

It might be even possible to do that on-the-fly in the inline assembly.

]]> By: LeDude http://blog.hartwork.org/?p=86&cpage=1#comment-3589 LeDude Sat, 06 Oct 2007 23:29:16 +0000 http://blog.hartwork.org/?p=86#comment-3589 You could also try gas2masm. Converts gnu assembly code into microsoft-compatible assembly code. I know it from the Quake source code, therefore I don't know whether it supports the latest and greatest assembly features (SSE etc.). You could also try gas2masm. Converts gnu assembly code into microsoft-compatible assembly code.
I know it from the Quake source code, therefore I don’t know whether it supports the latest and greatest assembly features (SSE etc.).

]]> By: berkus http://blog.hartwork.org/?p=86&cpage=1#comment-3429 berkus Thu, 04 Oct 2007 16:51:52 +0000 http://blog.hartwork.org/?p=86#comment-3429 I wonder why not use nasm, which has the same syntax on all x86 platforms. Then you will only need to maintain C interface, which is pretty stable between all releases of GCC and MSVC. I wonder why not use nasm, which has the same syntax on all x86 platforms.
Then you will only need to maintain C interface, which is pretty stable between all releases of GCC and MSVC.

]]> By: Fred P. http://blog.hartwork.org/?p=86&cpage=1#comment-3389 Fred P. Thu, 04 Oct 2007 02:56:55 +0000 http://blog.hartwork.org/?p=86#comment-3389 After looking at the documentation, YASM is what you want, it compiles assembly code from AT&T/gas style and can produce .OBJ files for Win32 and Win64 compatible with MSVC. See -f format in: http://www.tortall.net/projects/yasm/manual/html/manual.html#running-objfmt Here's the complete manual: http://www.tortall.net/projects/yasm/manual/html/manual.html The only thing is your code must not have inline assembly, the assembly must be in a seperate file. After looking at the documentation, YASM is what you want, it compiles assembly code from AT&T/gas style
and can produce .OBJ files for Win32 and Win64 compatible with MSVC.

See -f format in:
http://www.tortall.net/projects/yasm/manual/html/manual.html#running-objfmt

Here’s the complete manual:
http://www.tortall.net/projects/yasm/manual/html/manual.html

The only thing is your code must not have inline assembly, the assembly must be in a seperate file.

]]> By: Fred P. http://blog.hartwork.org/?p=86&cpage=1#comment-3387 Fred P. Thu, 04 Oct 2007 02:29:23 +0000 http://blog.hartwork.org/?p=86#comment-3387 Here's some more projects you might want to look into: http://lists.cs.uiuc.edu/pipermail/llvmdev/2005-July/004546.html http://www.tortall.net/projects/yasm/ http://www.tortall.net/projects/yasm/browser/trunk/yasm MASM writer (tgz file) http://lists.cs.uiuc.edu/pipermail/llvmdev/2005-July/004546.html Have fun Here’s some more projects you might want to look into:

http://lists.cs.uiuc.edu/pipermail/llvmdev/2005-July/004546.html

http://www.tortall.net/projects/yasm/
http://www.tortall.net/projects/yasm/browser/trunk/yasm

MASM writer (tgz file)
http://lists.cs.uiuc.edu/pipermail/llvmdev/2005-July/004546.html

Have fun

]]> By: chehrlic http://blog.hartwork.org/?p=86&cpage=1#comment-3335 chehrlic Wed, 03 Oct 2007 10:14:48 +0000 http://blog.hartwork.org/?p=86#comment-3335 I also think that nasm would be much better than maintaining two sources. I also think that nasm would be much better than maintaining two sources.

]]> By: Laerte http://blog.hartwork.org/?p=86&cpage=1#comment-3334 Laerte Wed, 03 Oct 2007 09:56:07 +0000 http://blog.hartwork.org/?p=86#comment-3334 Do you really have to use inline assembly? Why don't use separated files that can be assembled with nasm or another free assembler, avaiable to many diferent OS on x86 (Windows, Linux, *BSD, Solaris)? I think some of them can use AT&T format. Do you really have to use inline assembly?

Why don’t use separated files that can be assembled with nasm or another free assembler, avaiable to many diferent OS on x86 (Windows, Linux, *BSD, Solaris)?

I think some of them can use AT&T format.

]]>