Re: Handle macros like TARGET_OS_CPP_BUILTINS for non C-family frontends

2010-09-26 Thread Joseph S. Myers
On Sun, 26 Sep 2010, FX wrote: > How can we fix this? The only way I see would be to have two macros > instead of TARGET_OS_CPP_BUILTINS: one that will be used for > source-preprocessing in all languages (maybe keeping the name > TARGET_OS_CPP_BUILTINS), and one that will be used only for C-fam

Re: Handle macros like TARGET_OS_CPP_BUILTINS for non C-family frontends

2010-09-26 Thread Steven Bosscher
On Sun, Sep 26, 2010 at 4:21 PM, FX wrote: > How can we fix this? The only way I see would be to have two macros > instead of TARGET_OS_CPP_BUILTINS: one that will be used for source- > preprocessing in all languages (maybe keeping the name > TARGET_OS_CPP_BUILTINS), and one that will be used only