[Bug target/45261] Doesn't indicate failure status when it doesn't support (attiny2313A)

["j at uriah dot heep dot sax dot de" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #4 from j at uriah dot heep dot sax dot de  2010-08-12 09:54 -------
(In replay to comment #1)
> That should most likely be an error instead of just a fprintf.

Agreed.  What surprises me a bit that I've been under the impression
this used to work in previous releases:

[part of avr-libc's config.log]
  configure:6074: checking if avr-gcc has support for attiny461a
  configure:6090: avr-gcc -c -mmcu=attiny461a  conftest.c >&5
  Known MCU names:
    avr1 avr2 avr25 avr3 avr31 avr35 avr4 avr5 avr51 avr6 avrxmega1
  [...]
  Assembler messages:
  Fatal error: unknown MCU: attiny461a

  configure:6097: $? = 1
  configure: failed program was:
  | /* confdefs.h.  */
  | #define PACKAGE_NAME "avr-libc"
  | #define PACKAGE_TARNAME "avr-libc"
  | #define PACKAGE_VERSION "1.6.8"
  | #define PACKAGE_STRING "avr-libc 1.6.8"
  | #define PACKAGE_BUGREPORT "avr-libc-dev@nongnu.org"
  | #define PACKAGE "avr-libc"
  | #define VERSION "1.6.8"
  | /* end confdefs.h.  */
  | 
  configure:6116: result: no
[/config.log]

However, if I parse these messages correctly, GCC probably never
really rejected the unknown -mmcu option, instead it has only
incidentally been rejected because in turn, the assembler eventually
cmoplained.

I agree that it should already be the compiler's business to cause an
error exit status (by turning the fprintf() into an error()).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45261