[PATCH] Generalize overriding mechanism for debug info output options defaults

Jeff Law law@redhat.com
Thu Aug 18 14:41:00 GMT 2016


On 08/18/2016 08:01 AM, Pierre-Marie de Rodat wrote:
> On 08/18/2016 11:40 AM, Jakub Jelinek wrote:
>> I believe that is the preferred way, rather than macros.
>> The macros are yet another thing that would need to be undone if we ever
>> start supporting multiple targets in the same binary.
>> I don't see any advantages of introducing the macros.
>
> Ah, I understand, thank you. We debated a bit internally about whether
> one was better than the other, so thank you for the rationale!
>
> By the way, are there “official” plans to support multiple targets in
> the same binary at some point, by the way? It’s the first time I hear
> about it (that would be nice!).
It's pie in the sky right now, but it's something many of us want to see 
happen.  To that end we're trying to steer away from certain problematic 
idioms (like using macros to conditionalize behavior) towards schemes 
that would work in that world (hooks).

One good way to start thinking about this stuff is what would need to 
change to support a world where the target (or front-end) were a DSO and 
replaceable.

jeff




More information about the Gcc-patches mailing list