Re: Support for SDCC (small device C compiler)

[Paul Eggert]

Ralf Wildenhues <address@hidden> writes:

> [1] "binary" because what it generates is an interesting string of
> colons followed by runs of characters that all belong to the hexadecimal
> system.

My understanding is that an .ihx file is neither binary or executable.
You need to feed it to another program to make an executable binary
file.

>       * lib/autoconf/lang.m4 (_AC_COMPILER_OBJEXT_REJECT): Add
>       .adb, .asm, .cdb, .dump, .lnk, .lst, .mem, .rst, and .sym,
>       for the Small Device C Compiler (sdcc).
>       (_AC_COMPILER_EXEEXT_REJECT): Likewise, add .rel.
>       Report by Kallol Borah <address@hidden>.

http://sdcc.sourceforge.net/doc/sdccman.html/node41.html says
that there are many different extensions beginning with .dump,
so that the pattern should be *.dump* and not *.dump.

It also says that sdcc optionally generates a file with no extension,
e.g., "cc foo.c" creates a file named "foo." that is an AOMF or AOMF51
file.  And this file apparently is an "executable"?  What will/should
the code do with that?  Count it as an executable?