Menu

#3744 sdas8051 is falling.

open
nobody
None
MCS51
5
2024-06-28
2024-06-15
No

The include directive causes the compiler to crash.

type SDCC_STARTUP_M5.s

.include 12345678

sdas8051 -l -o -s -a SDCC_STARTUP_M5.s

sdcc -v
SDCC : mcs51/z80/z180/r2k/r2ka/r3ka/sm83/tlcs90/ez80_z80/z80n/r800/ds390/pic16/pic14/TININative/ds400/hc08/s08/stm8/pdk13/pdk14/pdk15/mos6502/mos65c02 TD- 4.4.0 #14620 (MINGW64)
published under GNU General Public License (GPL)

Related

Bugs: #3763

Discussion

  • Janko Stamenović

    The one I've recompiled here doesn't crash. I've built it on # Ubuntu 22.04.4 LTS with these two lines in the sdas\as6808 directory, after the ./configure for sdcc cross compilation succeeded before (where the goal was not to build sdcc, just for the configure or make to produce whatever sdas binaries would need)

    x86_64-w64-mingw32-gcc-posix  -O2 -Wall -o sdas8051 -DSDCDB -DNOICE -DINDEXLIB -I. -I../.. -I./../../support/util -I ../asxxsrc/ i51pst.c i51mch.c i51adr.c ../asxxsrc/asdbg.c ../asxxsrc/asdata.c ../asxxsrc/asexpr.c ../asxxsrc/aslex.c ../asxxsrc/aslist.c ../asxxsrc/asmain.c ../asxxsrc/asout.c ../asxxsrc/assubr.c ../asxxsrc/assym.c ../asxxsrc/asmcro.c ../asxxsrc/sdas.c ../asxxsrc/strcmpi.c ../../support/util/dbuf.c ../../support/util/dbuf_string.c
    x86_64-w64-mingw32-strip sdas8051.exe
    

    I've uploaded the binary here:

    https://sourceforge.net/projects/sdcc-z80n-mingw64-binaries/files/other/sdas8051-win64-binaries.7z/download

    I've also rebuilt the sdasz80.exe with make sdcc-as (I don't know how to say "make only one version, that's after I've performed ./configure --host x86_64-w64-mingw32 --disable-z180-port ... etc )

    https://sourceforge.net/projects/sdcc-z80n-mingw64-binaries/files/sdasz80-win64-binary-nocrash.7z/download

    The minimal input for the sdasz80 version from the binary from the sdcc w64 distribution to cause crash is even a single "wrong" instruction like:

    retnn
    

    In the attached picture: first, after my recompilation, second the original.

    What could be the case in for these more official builds? If I'd guess: either something misconfigured on these computers where it is built or, also on these, some dependency on some bug that was corrected on Ubuntu 22.04.4 LTS. But I really don't know.

     

Log in to post a comment.