constructor priority support for stormy16

[Richard Henderson]

On Fri, Aug 31, 2001 at 08:43:24AM -0700, Geoffrey Keating wrote:
> (The aim of all this is to have the .ctors* and .dtors* sections
> readonly.)

Let's solve this a different way then.  I do not want these
macros needlessly re-propagating as functions.

How about target macros

   READONLY_CONSTRUCTORS
   READONLY_EXCEPTION_HANDLING

that would evaluate true when constructors (.ctors, .dtors, .jcr)
or exception data (.eh_frame, .gcc_except_table) can be marked
read-only.  This macro would have to be (re-)defined based on 
IN_LIBGCC2 so that crtstuff can define the variables the same way.


r~