On Tue, 22 Mar 2011, Hans-Peter Nilsson wrote: > > CRIS > > A closer inspection will show that it's only the subtarget > cris-*-aout. IIRC support for this target was removed for GCC, > it'd probably be a good idea to do the same here at the > top-level for the other projects (newlib, binutils, gdb). (For > the record, generating cris-aout output should still be possible > through cris-elf-objcopy.)
I do intend as part of toplevel cleanup following up on removal of deprecated targets to cleanup such cases relating to targets removed from GCC (since whether or not any bit of the src repository supports them, GCC-specific configure code for them certainly isn't needed at toplevel). > > and MMIX targets list Fortran in unsupported languages? I didn't > > think the Fortran libraries had any porting issues, unlike Java and Go and > > Ada.) > > For MMIX, the issues I mentioned at > <http://gcc.gnu.org/ml/gcc-patches/2004-11/msg00572.html> are > presumably fixed, but pragmatically the interest level for Those look like newlib-target issues, not MMIX-target issues, in any case. > fortran on MMIX is ...undetectable. (Prove me wrong: I > challenge anyone to send gcc-testresults@ with it enabled and > the mmixware simulator installed.) So, for the time being I'm > not prepared to add that as something that is expected to be > maintained. It's not a matter of "expected to be maintained", it's a matter of targets only being different from other targets where there is a clear reason for that difference (an important feature of the GNU toolchain is consistency between targets). I expect most users of many targets to be using --enable-languages=c,c++ (or just c) - but I see no reason for the defaults for this target to be different from those for many other newlib-using targets. -- Joseph S. Myers jos...@codesourcery.com
