James Carlson wrote:
> Garrett D'Amore wrote:
>
>> New objects built on OpenSolaris ought to use a non-exec stack by
>> default. Without user intervention. I think executable stacks should
>> be an opt-in feature.
>>
>
> +1
>
> If that's the actual path that will (soon?) be taken, then I no longer
> care about hanging my hat on the v2 syntax.
>
>
>> So I guess what I'm talking about is a change in the default, globally.
>> I presume its possible to do this so the default is applied at compile
>> time, rather than load time? (That would address the concern of
>> breakage of older binaries.)
>>
>
> There are actually three 'times' involved -- compilation (cc), link
> editing (ld), and link-load (ld.so.1). It's during that second one that
> mapfiles are of interest and that the segment flags are set.
>
>
>> Btw, I'm of the mind that it may be questionable to retain the old v1
>> mapfile syntax for very long. As indicated, not many people are using
>> it, and we really shouldn't have to carry around baggage ~forever. I
>> don't think the mapfile syntax was ever officially part of our source
>> compatibility story. :-)
>>
>
> I think that's a step too far. Yes, they're Committed interfaces and,
> no, it would not be good to have them go away.
>
But wouldn't a tool to convert them answer the requirement for Committed
support? I don't think the specific compiler command lines are part of
that Committed interface, but perhaps I'm wrong. And I think I'd propose
marking them Obsolete (at least) as part of this.
- Garrett
