[Bug target/45345] In function `mips16_build_function_stub' undefined reference to `ASM_OUTPUT_DEF'

["rsandifo at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45345

--- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> 2011-05-28 21:16:17 UTC ---
(In reply to comment #6)
> No -- as in this, this isn't unused, ought not be deprecated.
> You mentioned 32bit mips/a.out -- sure, maybe that is unused.
>   I assume a.out is almost unused across the board.
> But 64bit mips/elf is used.
> 
> Now, granted, OpenBSD I believe is sticking back with gcc 4.2?3/GPL2 so
> probably doesn't care what you do with 4.5.

Well, this isn't about 4.5, it's about 4.7.  And the idea
is that 4.7 will still accept mips*-*-openbsd* when configured
with --enable-obselete.  (Although that's only a technicality
given that the port doesn't build.)

But if OpenBSD are sticking with 4.2, someone else needs to
do the work to fix it for mainline, and to be prepared to
continue to care for it going forward.  There's no point
keeping a port that doesn't build for year after year.

> But surely Linux is using mips64/elf and probably also mips32/elf?
> (and Irix, if it is still supported)

Sure, but they do all the things that an ELF port should do.
As you note in comment #2, OpenBSD doesn't.  This is not about
deprecating MIPS on ELF.

> There is pretty recent hardware development here, you know, Loongson.

Again, I'm not sure what you mean.  What bearing does Loongson
have on the OpenBSD port?

Loongson as an _architecture_ is of course supported, and people
are happily using on GNU/Linux.  But as with all these things
the reason that Loongson is a supported architecture is that
people have been prepared to submit patches for it and fix bugs.

Richard