Problems in latest YASM snapshot

Peter Johnson peter at tortall.net
Fri Dec 2 09:29:32 PST 2005


Catalin,

On Fri, 2 Dec 2005, Catalin Ionescu wrote:
> 1) "section" directive for Win32 output format has a bug causing an
> exception. The lack of documentation made me look into the source files
> to determine the exact format and tried the following three possibilities:
>
>  - section .text execute read align 16
>  - section .text execute read align16
>  - section .text execute read align=16
>
> The first one crashes the assembler. The second one is properly signaled
> as error. The third one warns me that the flags I've just specified are
> ignored as the section is re-declared - and that is surely not the case!

I'll take a look at this.  It should be straightforward to fix.

> 2) Relative jumps byte offsets are written 0 in the listing file, though
> they are correct in the object file. I have no situation with dword
> offsets and thus I can't tell if that one is working properly.

This is a known bug with listing files at the moment.  The fix is waiting 
on an optimizer rewrite I'm working on.  Is this critical for you?

> 3) When accessing local procedure variables on the stack I use
> EBP+offset code generated by a special macro. For every line where I
> access variables on the stack (arguments and/or local variables) I get
> the following warning:
>
> "rc_rtl.nas:52: warning: invalid displacement size; fixed"
>
> The generated code is correct, but with some source files I get 1000+
> warnings!

Can you send a copy of the macro?  I think I know what's happening but I 
need to validate my theory.

Thanks,
Peter


More information about the yasm-devel mailing list