binutils-2.16 news

binutils-2.16 news

[Alan Modra]

	* NEWS: Mention unsupported targets and new readelf option.

Index: binutils/NEWS
===================================================================
RCS file: /cvs/src/src/binutils/NEWS,v
retrieving revision 1.48
diff -u -p -r1.48 NEWS
--- binutils/NEWS	19 Jan 2005 23:43:00 -0000	1.48
+++ binutils/NEWS	20 Apr 2005 07:11:22 -0000
@@ -1,5 +1,59 @@
 -*- text -*-
 
+* Binutils-2.16 will be the last release for a number of targets due to
+  lack of maintenance (of course, if maintainers step up, then this list
+  will change!).  The targets are:
+
+    a29k-*-*
+    d10v-*-*
+    d30v-*-*
+    dlx-*-*
+    h8300-*-coff
+    h8300-*-rtems*
+    h8500-*-coff
+    h8500-*-rtems*
+    i370-*-*
+    i960-*-*
+    i960-*-bout
+    i960-*-coff
+    i960-*-nindy*
+    i960-*-rtems*
+    i960-*-vxworks*
+    i960-*-vxworks5.*
+    i960-*-vxworks5.0
+    m68k-*-coff
+    m68k-*-hpux*
+    m68k-*-linux*aout*
+    m68k-*-rtemscoff*
+    m68k-*-sunos*
+    m68k-*-sysv*
+    m68k-*-vxworks*
+    m68k-apollo-*
+    m68k-apple-aux*
+    m68k-bull-sysv3*
+    m68k-ericsson-ose
+    m68k-motorola-sysv*
+    m88k-*-*					(*)
+    mn10200-*-*
+    openrisc-*-*
+    or32-*-*
+    or32-*-coff
+    pj*-*-*
+    sh-*-coff*
+    sh-*-rtemscoff*
+    tic80-*-*
+    vax-*-bsd*					(*)
+    vax-*-netbsd* excluding vax-*-netbsdelf	(*)
+    vax-*-ultrix*				(*)
+    w65-*-*
+    xscale-*-coff
+    *-*-linux*aout*
+    *-*-linux*oldld
+
+    (*) bfd and opcodes support will be kept.
+
+* Add "-g/--section-groups" to readelf to display section groups.
+
 * objcopy recognizes two new options --strip-unneeded-symbol and
   --strip-unneeded-symbols, namely for use together with the wildcard
   matching the original --strip-symbol/--strip-symbols provided, but

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

Re: binutils-2.16 news

[Ralf Corsepius]

On Wed, 2005-04-20 at 16:44 +0930, Alan Modra wrote:
> 	* NEWS: Mention unsupported targets and new readelf option.

> +* Binutils-2.16 will be the last release for a number of targets due to
> +  lack of maintenance (of course, if maintainers step up, then this list
> +  will change!).  The targets are:

> +    h8300-*-coff
> +    h8300-*-rtems*
Does this mean you are going to remove the entire h8 series or why are
you planning to remove these 2 targets?

Ralf

Re: binutils-2.16 news

[Nick Clifton]

Hi Ralf,

>>+* Binutils-2.16 will be the last release for a number of targets due to
>>+  lack of maintenance (of course, if maintainers step up, then this list
>>+  will change!).  The targets are:
> 
> 
>>+    h8300-*-coff
>>+    h8300-*-rtems*
> 
> Does this mean you are going to remove the entire h8 series or why are
> you planning to remove these 2 targets?

No, the h8300-elf port is still going to be valid.  It is just that at 
the moment it looks like nobody wants to step up and champion the 
h8300-coff and h8300-rtems ports...

Cheers
   Nick

Re: binutils-2.16 news

[Ralf Corsepius]

On Wed, 2005-04-20 at 10:39 +0100, Nick Clifton wrote:
> Hi Ralf,
> 
> >>+* Binutils-2.16 will be the last release for a number of targets due to
> >>+  lack of maintenance (of course, if maintainers step up, then this list
> >>+  will change!).  The targets are:
> > 
> > 
> >>+    h8300-*-coff
> >>+    h8300-*-rtems*
> > 
> > Does this mean you are going to remove the entire h8 series or why are
> > you planning to remove these 2 targets?
> 
> No, the h8300-elf port is still going to be valid.  It is just that at 
> the moment it looks like nobody wants to step up and champion the 
> h8300-coff and h8300-rtems ports...
OK, I understand, the reason is coff?

I'll have to check if rtems can change to elf.

Thanks,
	Ralf

Re: binutils-2.16 news

[Nick Clifton]

Hi Ralf,

>>No, the h8300-elf port is still going to be valid.  It is just that at 
>>the moment it looks like nobody wants to step up and champion the 
>>h8300-coff and h8300-rtems ports...
> 
> OK, I understand, the reason is coff?
> 
> I'll have to check if rtems can change to elf.

Or just shout loudly enough.  The other reason for publishing that list 
of proposed ports to deprecate was to find out if anybody cared.  If you 
care about the h8300-rtems port and if you believe that it has a future, 
then we will remove it from the depcreated list.  (Even better would be 
if you volunteered to maintain it).

Cheers
   Nick

Re: binutils-2.16 news

[Alan Modra]

On Wed, Apr 20, 2005 at 12:16:11PM +0200, Ralf Corsepius wrote:
> On Wed, 2005-04-20 at 10:39 +0100, Nick Clifton wrote:
> > >>+    h8300-*-coff
> > >>+    h8300-*-rtems*
> > > 
> > > Does this mean you are going to remove the entire h8 series or why are
> > > you planning to remove these 2 targets?
> > 
> > No, the h8300-elf port is still going to be valid.  It is just that at 
> > the moment it looks like nobody wants to step up and champion the 
> > h8300-coff and h8300-rtems ports...
> OK, I understand, the reason is coff?

No, the reason is a non-BFD_ASSEMBLER gas port.  I want to rip out all
the old non-BFD_ASSEMBLER gas code, so unless the tc files are converted
over to BFD_ASSEMBLER they will no longer compile.

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

Re: binutils-2.16 news

[Ralf Corsepius]

On Thu, 2005-04-21 at 12:50 +0930, Alan Modra wrote:
> On Wed, Apr 20, 2005 at 12:16:11PM +0200, Ralf Corsepius wrote:
> > On Wed, 2005-04-20 at 10:39 +0100, Nick Clifton wrote:
> > > >>+    h8300-*-coff
> > > >>+    h8300-*-rtems*
> > > > 
> > > > Does this mean you are going to remove the entire h8 series or why are
> > > > you planning to remove these 2 targets?
> > > 
> > > No, the h8300-elf port is still going to be valid.  It is just that at 
> > > the moment it looks like nobody wants to step up and champion the 
> > > h8300-coff and h8300-rtems ports...
> > OK, I understand, the reason is coff?
> 
> No, the reason is a non-BFD_ASSEMBLER gas port.  I want to rip out all
> the old non-BFD_ASSEMBLER gas code, so unless the tc files are converted
> over to BFD_ASSEMBLER they will no longer compile.
Now, you've lost me.

AFAIU, this would affect h8300-*-elf, too, i.e. you'd be removing the
h8300 port as a whole.

Ralf

Re: binutils-2.16 news

[Daniel Jacobowitz]

On Thu, Apr 21, 2005 at 05:49:26AM +0200, Ralf Corsepius wrote:
> On Thu, 2005-04-21 at 12:50 +0930, Alan Modra wrote:
> > On Wed, Apr 20, 2005 at 12:16:11PM +0200, Ralf Corsepius wrote:
> > > On Wed, 2005-04-20 at 10:39 +0100, Nick Clifton wrote:
> > > > >>+    h8300-*-coff
> > > > >>+    h8300-*-rtems*
> > > > > 
> > > > > Does this mean you are going to remove the entire h8 series or why are
> > > > > you planning to remove these 2 targets?
> > > > 
> > > > No, the h8300-elf port is still going to be valid.  It is just that at 
> > > > the moment it looks like nobody wants to step up and champion the 
> > > > h8300-coff and h8300-rtems ports...
> > > OK, I understand, the reason is coff?
> > 
> > No, the reason is a non-BFD_ASSEMBLER gas port.  I want to rip out all
> > the old non-BFD_ASSEMBLER gas code, so unless the tc files are converted
> > over to BFD_ASSEMBLER they will no longer compile.
> Now, you've lost me.
> 
> AFAIU, this would affect h8300-*-elf, too, i.e. you'd be removing the
> h8300 port as a whole.

case ${fmt} in
  elf | ecoff | multi | som)
    bfd_gas=yes
    ;;
esac

No, all ELF targets are BFD_ASSEMBLER.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: binutils-2.16 news

[Joel Sherrill <joel@OARcorp.com>]

Ralf Corsepius wrote:
> On Wed, 2005-04-20 at 10:39 +0100, Nick Clifton wrote:
> 
>>Hi Ralf,
>>
>>
>>>>+* Binutils-2.16 will be the last release for a number of targets due to
>>>>+  lack of maintenance (of course, if maintainers step up, then this list
>>>>+  will change!).  The targets are:
>>>
>>>
>>>>+    h8300-*-coff
>>>>+    h8300-*-rtems*
>>>
>>>Does this mean you are going to remove the entire h8 series or why are
>>>you planning to remove these 2 targets?
>>
>>No, the h8300-elf port is still going to be valid.  It is just that at 
>>the moment it looks like nobody wants to step up and champion the 
>>h8300-coff and h8300-rtems ports...
> 
> OK, I understand, the reason is coff?
> 
> I'll have to check if rtems can change to elf.

Ralf.. There is no reason I know that the h8300 can't be elf.

> Thanks,
> 	Ralf
> 
> 


--joel

2.16 doc update (Re: binutils-2.16 news)

[H. J. Lu]

On Wed, Apr 20, 2005 at 04:44:53PM +0930, Alan Modra wrote:
> 	* NEWS: Mention unsupported targets and new readelf option.
> 
> +
> +* Add "-g/--section-groups" to readelf to display section groups.
> +

Here is also some doc update:

http://sourceware.org/ml/binutils/2005-04/msg00040.html

H.J.

Re: 2.16 doc update (Re: binutils-2.16 news)

[Daniel Jacobowitz]

On Wed, Apr 20, 2005 at 07:40:28AM -0700, H. J. Lu wrote:
> On Wed, Apr 20, 2005 at 04:44:53PM +0930, Alan Modra wrote:
> > 	* NEWS: Mention unsupported targets and new readelf option.
> > 
> > +
> > +* Add "-g/--section-groups" to readelf to display section groups.
> > +
> 
> Here is also some doc update:
> 
> http://sourceware.org/ml/binutils/2005-04/msg00040.html

The changelog is wrong; the NEWS entry isn't for -N.  -N isn't in 2.16,
right?

The binutils.texi bits are fine for 2.16, though.  Please commit.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Re: binutils-2.16 news

[Jan Beulich]

As far as I remember either you or Nick or Ian provided me with a list of targets one would ideally test against when making changes of global effect. Quite a number of these are listed here. I thus wonder whether there isn't (and if not, couldn't be) a place where a list of "primary" targets is maintained (which should clearly be free of targets already deprecated), so one could derive automated building/testing of those targets (or a subset, say all ELF ones) from it.

Jan

>>> Alan Modra <amodra@bigpond.net.au> 20.04.05 09:14:53 >>>
	* NEWS: Mention unsupported targets and new readelf option.

Index: binutils/NEWS
===================================================================
RCS file: /cvs/src/src/binutils/NEWS,v
retrieving revision 1.48
diff -u -p -r1.48 NEWS
--- binutils/NEWS	19 Jan 2005 23:43:00 -0000	1.48
+++ binutils/NEWS	20 Apr 2005 07:11:22 -0000
@@ -1,5 +1,59 @@
 -*- text -*-
 
+* Binutils-2.16 will be the last release for a number of targets due to
+  lack of maintenance (of course, if maintainers step up, then this list
+  will change!).  The targets are:
+
+    a29k-*-*
+    d10v-*-*
+    d30v-*-*
+    dlx-*-*
+    h8300-*-coff
+    h8300-*-rtems*
+    h8500-*-coff
+    h8500-*-rtems*
+    i370-*-*
+    i960-*-*
+    i960-*-bout
+    i960-*-coff
+    i960-*-nindy*
+    i960-*-rtems*
+    i960-*-vxworks*
+    i960-*-vxworks5.*
+    i960-*-vxworks5.0
+    m68k-*-coff
+    m68k-*-hpux*
+    m68k-*-linux*aout*
+    m68k-*-rtemscoff*
+    m68k-*-sunos*
+    m68k-*-sysv*
+    m68k-*-vxworks*
+    m68k-apollo-*
+    m68k-apple-aux*
+    m68k-bull-sysv3*
+    m68k-ericsson-ose
+    m68k-motorola-sysv*
+    m88k-*-*					(*)
+    mn10200-*-*
+    openrisc-*-*
+    or32-*-*
+    or32-*-coff
+    pj*-*-*
+    sh-*-coff*
+    sh-*-rtemscoff*
+    tic80-*-*
+    vax-*-bsd*					(*)
+    vax-*-netbsd* excluding vax-*-netbsdelf	(*)
+    vax-*-ultrix*				(*)
+    w65-*-*
+    xscale-*-coff
+    *-*-linux*aout*
+    *-*-linux*oldld
+
+    (*) bfd and opcodes support will be kept.
+
+* Add "-g/--section-groups" to readelf to display section groups.
+
 * objcopy recognizes two new options --strip-unneeded-symbol and
   --strip-unneeded-symbols, namely for use together with the wildcard
   matching the original --strip-symbol/--strip-symbols provided, but

-- 
Alan Modra
IBM OzLabs - Linux Technology Centre

Re: binutils-2.16 news

[Nick Clifton]

Hi Jan,

> As far as I remember either you or Nick or Ian provided me with a list of 
 > targets one would ideally test against when making changes of global 
effect.
 > Quite a number of these are listed here.

Note - those lists of targets were intended to cover the vast majority 
of targets supported by binutils, even those without maintainers.  The 
intention was to make sure that global changes did not break anything, 
even unmaintained ports.

> I thus wonder whether there isn't (and if not, couldn't be) a place where 
 > a list of "primary" targets is maintained (which should clearly be free
 > of targets already deprecated),

This could be deduced from the list of maintainers in the 
binutils/MAINTAINERS file.

Cheers
   Nick