#117 (OBJ32 warnings) – The Yasm Modular Assembler Project

Ticket #117 (new defect)

Opened 14 months ago

Last modified 13 months ago

OBJ32 warnings

Reported by: pg@… Owned by:
Priority: P1 Milestone:
Component: Parser: NASM-compatible Version: 0.6.0
Severity: minor Keywords:
Cc:

Description

yasm complains about the USE32 specification that is used in nasm-style sourcecode quite often: segment .code USE32 segment .data USE32 It´s just a warning, but I am wondering whether there is a good reason for that warning, or whether it can be turned off.

Attachments

Change History

comment:1 Changed 14 months ago by peter@…

Yasm does not yet support the original DOS .obj output format, and according to NASM's documentation, that's the only object format which supports those declarations, which is why Yasm's not implemented them yet.

If NASM has undocumented support for those declarations with other object formats (such as win32 or elf), we can certainly add them to Yasm as well. Let us know!

comment:2 Changed 13 months ago by pg@…

I guess that Nasm supports it for win32 (although I have no clear idea what purpose it actually has). And nasm definitely doesn´t complain or warn about it on elf format. I guess it might be an idea to just ignore it, and treat it as an optional hint, if you can´t make any use of it. It´s just a little bit annoying to get 100 warnings each time (since I have about 100 places in the sourcecode where it´s used ...)

Add/Change #117 (OBJ32 warnings)

Author



Action
as new
 
Note: See TracTickets for help on using tickets.