gnupic: gputils COFF directives


Previous by date: 10 Oct 2004 22:02:43 +0100 request for a doc writer, nisma.gmx.net
Next by date: 10 Oct 2004 22:02:43 +0100 Re: gputils COD fixes, Craig Franklin
Previous in thread: 10 Oct 2004 22:02:43 +0100 gputils COFF directives, Craig Franklin
Next in thread:

Subject: Re: gputils COFF directives
From: Craig Franklin ####@####.####
Date: 10 Oct 2004 22:02:43 +0100
Message-Id: <41695D4C.2020206@users.sourceforge.net>

I have further extended the COFF directives.  Here is the updated list:

.def  Create a COFF symbol
.dim  Create an auxiliary symbol
.direct Create direct messages for the simulator/emulator
.eof  End of File
.file Start of File
.ident Add a comment to the object file
.line  Create a line number
.type Specify the type of a gpasm generated COFF symbol

The manual has a full description of each one.

The .direct directive can be used to create BCDIRECT messages.  These 
were requested a few weeks ago.  With this directive the user can define 
assertions, printf, log, and simulator commands.  These symbols are 
written to the gplink generated COD file, as specified in version 4.0 of 
the COD spec.   gpvc can be used to view the messages.

gpsim will have to be modified to use the messages.

Craig Franklin wrote:

> I have added a set of directives to gputils for direct modification of 
> the COFF symbol table.  This will allow symbol types, optimizer 
> directives, simulator commands, ...  to be placed in the object files 
> at assembly time.
>
> These directives are an extension to gputils,  The names are old AS 
> directives that were used for COFF files.  However the syntax was 
> modified to conform with existing gpasm directives.  The directives are:
>
> .def  Create or modify a COFF symbol
> .dim  Create an auxiliary symbol
> .eof  End of File
> .file Start of File
> .line  Create a line number
>
> Three of the directives have been in gpasm for a while (#file, #eof, 
> #line).  I have changed them (.file, .eof, and .line) to  conform with 
> the new directives.  Otherwise they behave in the same manor.  The 
> leading "." on the names should keep them from colliding with symbol 
> definitions in most users source code.
>
> These features are advanced and require knowledge of how gputils 
> relocatable objects work. These features are intended to be used by 
> compilers. Nothing prevents them from being used with assembly.  I 
> have created a new header file (coff.inc) to simplify things for 
> assembly programmers.  It is not complete.  It will contain many 
> macros to perform common operations.
>
> The gputils manual has been updated.  Expect some changes over the 
> next couple of weeks.  Some of the details are still being decided.  I 
> will add a section on how to use the directives in a week or so.
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
>


Previous by date: 10 Oct 2004 22:02:43 +0100 request for a doc writer, nisma.gmx.net
Next by date: 10 Oct 2004 22:02:43 +0100 Re: gputils COD fixes, Craig Franklin
Previous in thread: 10 Oct 2004 22:02:43 +0100 gputils COFF directives, Craig Franklin
Next in thread:


Powered by ezmlm-browse 0.20.