Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#400 nasm warning in x86 windows builds

1.3.x
closed-fixed
Erik
None
5
2014-03-21
2013-07-19
Ozkan Sezer
No

During x86-windows builds using mingw or mingw-w64, nasm complains:
nasm.h:83: warning: COFF section names limited to 8 characters: truncating
I think the section .note.GNU-stack stuff aren't needed for win32
and should possibly be disabled just as they are for aout.

There are also warnings like:
bitreader_asm.nasm:593: warning: label alone on a line without a colon might be in error
cpu_asm.nasm:118: warning: label alone on a line without a colon might be in error
fixed_asm.nasm:309: warning: label alone on a line without a colon might be in error
lpc_asm.nasm:1508: warning: label alone on a line without a colon might be in error
stream_encoder_asm.nasm:156: warning: label alone on a line without a colon might be in error
... all of which are for "end" and actually harmless (just annoying.)

Discussion

  • Ozkan Sezer
    Ozkan Sezer
    2013-07-19

    And the thing is worse with OSX/x86 builds. Tried a linux-hosted cross-compile,
    got the following:
    nasm.h:83: panic: invalid section name .note.GNU-stack
    make[4]: *** [bitreader_asm.lo] Error 1

    After commenting out line #83 of nasm.h, got the following:
    bitreader_asm.nasm:36: warning: label alone on a line without a colon might be in error
    bitreader_asm.nasm:43: warning: label alone on a line without a colon might be in error
    bitreader_asm.nasm:52: error: The Mach-O output format does not support any special symbol types
    bitreader_asm.nasm:593: warning: label alone on a line without a colon might be in error
    make[4]: *** [bitreader_asm.lo] Error 1

    Notice that in both cases, the %error from line #54 of nasm.h does not trigger.

    The thing of course can be compiled by configuring --disable-asm-optimizations,
    no arguments there, but it would have been better if the configury had disabled
    it automagically.

     
  • Erik
    Erik
    2014-03-21

    Believe this to be fixed in:

    commit 3cea079a2f56357468f727fa4b6b35103426db17
    Author: Erik de Castro Lopo <erikd@mega-nerd.com>
    Date:   Tue Aug 13 19:18:40 2013 +1000
    
    Fix a couple of NASM warnings.
    
    Suggested by Ozkan Sezer <sezeroz@gmail.com>.
    
     
  • Erik
    Erik
    2014-03-21

    • status: open --> closed-fixed
    • assigned_to: Erik