Use of as_fatal

["Jan Beulich" <JBeulich at novell dot com>]

As the new 'macros dot' test has uncovered and (assuming the corresponding patch will get approved) 'macros purge' will too for some of the targets mentioned below, there is an issue with using as_fatal in places where the failure doesn't really appear to be fatal. Namely, when just an opcode isn't recognized (as would happen when one tries to reference a macro that isn't defined (yet/anymore), this condition is supposed to be hit. I am therefore wondering if the maintainers of the following targets could shed some light on the reasons why as_fatal is being used in this case by these targets; the outcome will help determine whether the target specific code should be changed or instead the target be excluded from running these tests.

hppa
ns32k
sparc
vax

Additionally a few other targets have problems here because of error message issuing differences; this can be taken into account in the output expectations, but I wonder whether there isn't a goal of having some standarddization in that respect between targets, namely with regard to

- issuing just a single error message for a single source error
- whether (and/or when/how) to re-issue error messages in the listing generation code

Thanks, Jan