On 08/18/2016 04:41 PM, Jeff Law wrote:
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).
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
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
On Thu, Aug 18, 2016 at 11:32:45AM +0200, Pierre-Marie de Rodat wrote:
> Currently, the VxWorks target overrides the defaults for debug info
> output options (DWARF version, strictness) in a target-specific options
> hook. This patch creates macros so that these defaults can be overriden
I
Hello,
Currently, the VxWorks target overrides the defaults for debug info
output options (DWARF version, strictness) in a target-specific options
hook. This patch creates macros so that these defaults can be overriden
in config headers. In particular, this will make it easier to have
different
