Improved error messages

[flamewing]

Some error messages given by AS are hilariously generic, even though the assembler has enough information to give a better diagnostic. Need to investigate the feasibility of improving those error messages, as well as how better to phrase them.

[Awuwunya]

Slso if I may add, AS will spam a ton of irrelevant errors sometimes if for example there is a problem with a previous 68k instruction. If there is a way to fix/reduce this it would help with diagnosing the actual issue at hand

[flamewing]

Two command line options that help with this are:

• -maxerrors <n>: instructs the assembler to terminate assembly after the given number of errors
• -Y: suppress all messages about out-of-branch conditions, once the necessity for another pass is given

Using -maxerrors 1 stops at the first error, instead of waiting for the count to reach 200 (the default) or finishing assembly; if you want to have a bit more leeway, maybe using 5 or 10 should suffice.

-Y reduces spam when you don't write all .b, .s, .w, or .l specifiers. It is a bit irrelevant for me because I use -r 2 (which errors out if a third pass is needed) and I write all specifiers.

[Awuwunya]

this should probably be standard in the Git AS disassemblies in that case, having max errors at 10 probably. I dont think they set a maximum? Still I think it might confuse new users, so having a setup which makes things the least confusing would help new people out