On Wed, Dec 07, 2016 at 08:46:32PM +0900, Oleg Endo wrote: > Hi, > > Yeah, my SH5/SH64 removal procedures might have been a little too > radical, sorry about that. However ... > > On Wed, 2016-12-07 at 09:10 +1030, Alan Modra wrote: > > I understand that config/ in the gcc repository is the master source > > for binutils-gdb config/. If that's the case then people removing > > gcc support for particular targets need to be careful about their > > config/ edits. If a target is still supported in binutils, then > > please don't rip out config/ support for the target. > > How exactly is this going to work when support for a configuration has > been removed from the compiler, but not from the configuration itself? > That's just confusing for the user and doesn't make sense, I believe.
The files in the config/ directory don't select which targets are supported by gcc. That selection is done in other files, like config.gcc. I don't see anything that would be confusing to users by leaving sh5 patterns in say config/picflag.m4. The config/* files are similar to config.guess and config.sub. Just as you do not touch config.guess and config.sub when removing a target from gcc support, so you should not need to modify config/*. -- Alan Modra Australia Development Lab, IBM
