Re: [rfc] Eliminate write_register from solib-sunos.c

["Ulrich Weigand" <uweigand at de dot ibm dot com>]

Mark Kettenis wrote:

> > In fact, this is very weird as those same bsd targets have solib-svr4.o
> > in their .mt files.  Which one is getting used in that case?  I'll try
> > to find out what's going on here ...
> 
> There are some a.out BSD targets that use solib-sunos.o.  In
> particular OpenBSD/m68k still uses it.  Interestingly enough, that
> target sets DECR_PC_AFTER_BREAK to 2.  I'll fire up my Quadra 800 and
> investigate somewhere later this week.

Thanks!  It looks like the following native targets use solib-sunos.o
(this works due to init-order for native targets only; a cross-target
would attempt to use solib-svr4.o):

arm*-*-netbsd* (except arm*-*-netbsdelf*)
sparc*-*-netbsd* (except sparc*-*-netbsdelf*)
vax*-*-netbsd* (except vax*-*-netbsdelf*)

  None of those define DECR_PC_AFTER_BREAK.

i[34567]86-*-netbsd* (except i[34567]86-*-netbsdelf*)
i[34567]86-*-openbsd[0-2].* | i[34567]86-*-openbsd3.[0-3]

  These define DECR_PC_AFTER_BREAK to 1.

m68*-*-netbsd* (except m68*-*-netbsdelf*)
m68*-*-openbsd*

  These define DECR_PC_AFTER_BREAK to 2, as you point out.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com