On Sat, Sep 12, 2009 at 11:56 PM, Bill Bumgarner <email@hidden> wrote:
> (An aside: Blocks start out on the stack for exactly this reason -- stack
> based blocks are tons and tons faster than requiring a chunk of heap)
Sure, allocating heap is costly; but I'm just talking about zeroing a
register or a stack slot. I'm surprised that carries much cost at all
on modern pipelined architectures. Anyway, it's a space versus time
tradeoff -- compiler option perhaps?
> On Sep 12, 2009, at 3:21 PM, Hamish Allan wrote:
>
>> Do you already have a simple "don't alter a base pointer if it's
>> marked __strong" rule?
>
> No and I'm not sure that overriding __strong to have another meaning makes a
> lot of sense.
I mean it in the documented sense: "a reference that is visible to the
garbage collector". If a function or method returns memory that is
visible to the garbage collector, and the programmer does not
explicitly alter the pointer returned, then neither should the
optimizer.
Hamish
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
