"Go" tools go 64-bit

Discussion in 'Windows 64bit' started by =?Utf-8?B?SmVyZW15IEdvcmRvbg==?=, Sep 17, 2005.

  1. The "Go" tools, GoAsm, GoLink and GoRC are all now in new versions capable of
    producing 64-bit programs which can be run on X64 (x86-64) processors (such
    as the AMD64 or EM64T) running under Windows XP64.
    The same versions of these tools work for both 32-bit or 64-bit assembly.

    All the 64-bit capable versions of these tools are currently beta versions
    and can be downloaded from here:-
    GoAsm 32/64-bit
    assembler (version 0.54.01 beta with documentation 310K)

    GoRC 32/64-bit
    resource compiler (version 0.90.0 beta 59K)

    GoLink 32/64-bit
    linker (version 0.26.2 beta with documentation 57K)

    Despite the differences between the 64-bit processors and their 32-bit
    counterparts, and between the x64 (Win64) operating system and Win32, using
    GoAsm to write 64-bit Windows programs is just as easy as it was in Win32.
    In fact, you can readily use the same source code to create executables for
    both platforms if you use GoAsm's enhanced instructions ARG and INVOKE and
    FRAME...ENDF, and conditional assembly for data sizes and structures. Then
    specify /x64 in the command line to make a 64-bit object file and /x86 to
    make a 32-bit one. GoLink automatically senses the type of object file to
    make the correct executable.
    See writing
    64-bit programs
    for details.
    You can still use these versions of the tools to make 32-bit executables
    using your existing source code, and there is no need to change anything. I
    have tried to minimise the switching to maintain speed.
    All these tools are still under development and all bug reports would be
    appreciated. The tools do not yet offer full support for 64-bit structured
    exception handling. This
    is in progress but I would welcome any ideas for an appropriate syntax to
    use. In 64-bit assembly it will be much easier for the assembler to offer
    automatic exception handling procedures. This is because exception handling
    is now table based (if an exception occurs, the system looks in a
    table in the executable to see if the program has its own handler). GoAsm
    might offer the ability to have a customised message delivered to the user,
    and/or a call or jump to your own exception handler, or "safe place".
    GoBug will be revised to enable it to debug 64-bit applications.

    See the Go tools website
    Jeremy Gordon
    The "Go" tools
    =?Utf-8?B?SmVyZW15IEdvcmRvbg==?=, Sep 17, 2005
    1. Advertisements

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. BP
    Dec 19, 2008
  2. Homer J. Simpson
    Jim Barry
    Jan 19, 2009
  3. David B.
    David B.
    Jan 20, 2009
  4. Lanwench [MVP - Exchange]
    Lanwench [MVP - Exchange]
    Jan 21, 2009
  5. sandi_ro
    Jan 28, 2009