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
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
Hi all,
I'm trying to see a way forward for PR 42954: when preprocessing Fortran source
files, we used to call the C preprocessor and run the Fortran compiler on the
generated file. We now use libcpp directly, but by doing so, we have lost a
good number of target-dependent CPP builtins that are
