[CFT] kill darwin encode_section_info

[Dale Johannesen]

On Tuesday, May 13, 2003, at 08:51  PM, Richard Henderson wrote:
> On Tue, May 13, 2003 at 06:34:18PM -0700, Dale Johannesen wrote:
>> I've seen it before, and I expect there's a good reason it was using
>> current_function_uses_pic_offset_table instead.  I see that several
>> other ports also use it.  So why not?
>
> Because it's less efficient.
>
> If you use current_function_uses_pic_offset_table, if any code
> *ever* exists that looks at symbolic info you are forced to load
> the pic register.  Even if the code that needed it is removed
> as dead.  Plus, to a large extent you get the life info for the
> pic register for free as a part of flow1.

Fair enough.  Actually I have a local patch that walks the RTL and
recomputes current_function_uses_pic_offset_table correctly from
the prolog, to get around this problem.  I agree that regs_used
is superior *if* it is reliable, which it hasn't been so far.