[Nasm-bugs] [ nasm-Bugs-2067837 ] Wrong addresses on public symbols

[SourceForge.net <no...@so...>]

Bugs item #2067837, was opened at 2008-08-22 12:47
Message generated for change (Comment added) made by fbkotler
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106208&aid=2067837&group_id=6208

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Assembler
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: A Fog (agnerfog)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong addresses on public symbols

Initial Comment:
Assembling the attached file produces an object file where the addresses of public symbols L1, L2, L3 are wrong by an offset of 2.

To reproduce: 
nasm -f win64 -o nasmerr1.obj nasmerr1.asm

then dump or disassemble.
The correct addresses of L1, L2, L3 should be 4, 5, 6.
The actual addresses are 6, 7, 8.

Nasm ver. 2.03.01

----------------------------------------------------------------------

>Comment By: Frank Kotler (fbkotler)
Date: 2008-08-24 18:21

Message:
Logged In: YES 
user_id=68913
Originator: NO

Hmmm... what's the "+2" on line 978 of assemble.c doing for us? Commenting
it out makes this go away. What's "right" there?

Best,
Frank



----------------------------------------------------------------------

Comment By: Frank Kotler (fbkotler)
Date: 2008-08-24 17:53

Message:
Logged In: YES 
user_id=68913
Originator: NO

Excellent! Thank you!

Back to our bug... is it my imagination, or does this error only occur on
AVX instructions (sandybridge)? I haven't checked extensively, but at least
*some* other instructions in that spot seem to give correct results, and
*some* other AVX instructions exhibit the problem... That's as far as I've
gotten (I'm *way* over my head here!)

Best,
Frank





----------------------------------------------------------------------

Comment By: A Fog (agnerfog)
Date: 2008-08-24 01:54

Message:
Logged In: YES 
user_id=1052480
Originator: YES

fbkotler wrote:
The only tool I've got that'll "dump" it is "objconv" (Very sweet, Sir!
Thank you! ...any chance of a "-fnasm" switch?).
You're lucky. I just added a -fnasm switch two days ago!

----------------------------------------------------------------------

Comment By: Frank Kotler (fbkotler)
Date: 2008-08-23 14:09

Message:
Logged In: YES 
user_id=68913
Originator: NO

Hello Mr. Fog,

Delighted to see you taking an interest in Nasm!

I can confirm this problem. The only tool I've got that'll "dump" it is
"objconv" (Very sweet, Sir! Thank you! ...any chance of a "-fnasm"
switch?). I can also see 6, 7, 8 in a raw hexdump of the .obj. (note that
the addresses in the code itself are okay)

Seems like a fairly serious bug!

Best,
Frank



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=106208&aid=2067837&group_id=6208