Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#397 Request z80 port to include which ralloc was used in .lst file

open
nobody
None
5
2013-08-19
2013-08-19
Brian Ruthven
No

It would be useful if the .lst file (and possibly the .asm file too) were to record whether --oldralloc was specified or not. When looking back over already compiled files, it's not obvious which was used, and when one is broken, it could save much time in diagnosing what was wrong. All that's needed is an additional comment, rather than a new directive similar to (or extending) .optsdcc.

Discussion

  • I would even go further, and suggest that .lst and .asm files for all ports include the full option string as a comment.

    Philipp

     
  • Brian Ruthven
    Brian Ruthven
    2013-08-19

    That sounds like a reasonable suggestion (assuming by "option string" you mean the command line used to call sdcc. It may be worth throwing in things like the current directory (i.e. where the source file came from) as well as any influential environment variables active at the time.

     
  • Borut Ražem
    Borut Ražem
    2013-08-19

    IMHO the .optsdcc shold contaion only ABI specific options, which --oldalloc probably is not.

    I agree with Philipp's proposal to include the command line options as a comment.

    Borut