[Bug]: non-static arrays stored in object file

[Mike Stump]

> From: Alexandre Oliva <oliva@dcc.unicamp.br>
> Date: 03 Aug 1999 01:03:09 -0300

> On Jul 29, 1999, mrs@wrs.com (Mike Stump) wrote:

> > Yes.  It is a simple bug in the port file that has a 4 line solution,
> > and probably the same 4 line soution across all targets, all ports.

> Care to explain?  I don't know what you're talking about.

Somewhere else in this thread, someone named the macros, and very
shortly there after, someone submitted the patches to add these macros
for a machine...  I'd hope that would be enough to explain this.  See
*BSS* in *.texi for more information.  *BSS* in the ChangeLog will
find the patches.

> What is the bug in the ports?

Not defining those macros.

> Why would it be a bad idea to generate common symbols for
> zero-initialized C++ variables unless strict compliance is
> requested?

Because that violates the C++ Standard.  Because things like ctor
ordering and dtor ordering become, uhm, interesting.  Because things
like shared libraries start to have interesting semantics with such
things, because the frontend no longer expects common to be used.

Sorry, there is no going back, there simply is no reason to do it.