This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Thu, Jun 13, 2002 at 10:12:20AM -0700, Zack Weinberg wrote: > On Thu, Jun 13, 2002 at 12:39:20PM -0400, Nathanael Nerode wrote: > > There seemed to be consensus that nobody was using or supporting vax-*-vms*. > > This obseletes it in gcc. Tested on i686-pc-linux-gnu, no changes caused. > > > > 2002-06-13 Nathanael Nerode <neroden@twcny.rr.com> > > * config.gcc (vax-*-vms*): Obsolete. > > * config/vax/xm-vms.h: Remove. > > * config/vax/vms.h: Remove. > > The normal procedure for obsoleting targets is that you *only* add the > entry to the case statement at the top of config.gcc; you leave > everything else alone until after a release has occurred. In other > words, you would only apply this bit. (And you need to update > gcc-3.2/changes.html to match.) Yes, I realized what I'd done about two seconds after I sent that mail. :-/ There's already an alternate patch sent in. > > > *** 221,226 **** > > --- 221,227 ---- > > | ns32k-*-netbsd* \ > > | ns32k-*-openbsd* \ > > | romp-*-openbsd* \ > > + | vax-*-vms* \ > > ) > > if test "x$enable_obsolete" != xyes; then > > echo "*** Configuration $machine is obsolete." >&2 > > However, for this target I am tempted to say that it's been broken for > several releases already and we should just take it out now. In that > case, the procedure would be to replace the "VAXen running VMS" stanza > from the big case statement with one that issues an unconditional > error message, like this: > > vax-*-vms*) # would otherwise be caught by vax-*-* > echo "*** Configuration $machine not supported" 1>&2 > exit 1 > ;; > > and then delete vax/vms.h, vax/xm-vms.h, and all references to VMS > from the remaining vax/* files. And update gcc-3.2/changes.html to > say that VAX/VMS was dropped, not just obsoleted. > > Can I get opinions on which should be done? If consensus is to just toast it now, I'll be happy to make up the patches. :-) --Nathanael
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |