> The patch is implemented within libcpp: any such conflict markers were > typically injected by tools that work on raw lines of unpreprocessed > text, so it seemed fitting to do it there. > > The error can be suppressed with -fno-detect-conflict-markers for > the case where you're using the compiler just for the C preprocessor > and some of the input files legitimately contain such character > sequences.
Could a new option be avoided (and maintain backwards compatibility) simply by not detecting this error when only preprocessing? Cheers, Manuel.
