Re: 4.4 deprecation proposals

2008-06-15 Thread Ben Elliston
On Sat, 2008-06-14 at 18:53 +, Joseph S. Myers wrote: > m68k-*-aout* > m68k-*-coff* These would be fine with me; there has been no interest in these targets in binutils-land for some time. Ben

Re: 4.4 deprecation proposals

2008-06-15 Thread Joseph S. Myers
On Sun, 15 Jun 2008, Ian Lance Taylor wrote: > My understanding is that Joseph is just talking about removing the > entries in config.gcc. He is not talking about removing the support > in the code, except perhaps for cases where there is no longer any > entry in config.gcc which requires that su

Re: 4.4 deprecation proposals

2008-06-15 Thread Ian Lance Taylor
DJ Delorie <[EMAIL PROTECTED]> writes: >> I thought DJGPP was i[34567]86-pc-msdosdjgpp*. I do not think >> having generic CPU-*-OBJFMT triplets that really refer to a >> particular OS is a good idea. It's only certain generic triplets >> I'm proposing to deprecate. > > DJGPP is ix86-pc-msdosdjgp

Re: 4.4 deprecation proposals

2008-06-15 Thread DJ Delorie
> I thought DJGPP was i[34567]86-pc-msdosdjgpp*. I do not think > having generic CPU-*-OBJFMT triplets that really refer to a > particular OS is a good idea. It's only certain generic triplets > I'm proposing to deprecate. DJGPP is ix86-pc-msdosdjgpp, yes. However, it's based on the ix86-coff

Re: 4.4 deprecation proposals

2008-06-15 Thread Joseph S. Myers
On Sun, 15 Jun 2008, DJ Delorie wrote: > "Joseph S. Myers" <[EMAIL PROTECTED]> writes: > > i[34567]86-*-coff* > > DJGPP is ix86-coff - how would this deprecation affect djgpp? I thought DJGPP was i[34567]86-pc-msdosdjgpp*. I do not think having generic CPU-*-OBJFMT triplets that really refer t

Re: 4.4 deprecation proposals

2008-06-15 Thread DJ Delorie
"Joseph S. Myers" <[EMAIL PROTECTED]> writes: > i[34567]86-*-coff* DJGPP is ix86-coff - how would this deprecation affect djgpp?

Re: 4.4 deprecation proposals

2008-06-14 Thread Manuel López-Ibáñez
2008/6/14 Joseph S. Myers <[EMAIL PROTECTED]>: > We need to consider what targets and other features, if any, to > deprecate or remove in GCC 4.4. > > I previously suggested the deprecation or removal of protoize and > fixproto , without If we remov