Re: [PATCH 0/4] baby step toward multi-target

[Pedro Alves <palves at redhat dot com>]

On 07/29/2014 03:49 PM, Tom Tromey wrote:

> However, it's probably useful as a starting point for the next attempt
> at multi-target.  In particular it's much less invasive than the earlier
> approach, and the "convert current_target to be a pointer" patch (the
> biggest one) was mostly done with a perl one-liner.

Yeah.

Hmm, kind of orthogonal, but not really, I wonder how far are we
to getting rid of the remaining target stack annoyances.  Like:

 #1 - Convert the remaining data fields to methods.  That seems it'll
      just be boring work.
 #2 - making the debug target a wrapping target around each target layer
      (as you suggested elsewhere).  That'll require make-target-delegates
      hacking.

That'd then make it possible to:

 #3 - eliminate the squashed current_target, replacing it with a pointer
      to the topmost target in the stack (mostly the same as your
      perl one-liner).

Is that in line with what you've been thinking?  I'm wondering whether
you found out in the more invasive branch that it's useful if
current_target is more than a struct target_ops pointer ?
(or "struct target *" after vtable-ification.)

Thanks,
Pedro Alves