This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/68029] Strange behavior of -fdiagnostics-color option
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 02 Nov 2015 14:06:28 +0000
- Subject: [Bug driver/68029] Strange behavior of -fdiagnostics-color option
- Auto-submitted: auto-generated
- References: <bug-68029-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68029
--- Comment #4 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
(In reply to JiÅÃ Engelthaler from comment #3)
> (In reply to Manuel LÃpez-IbÃÃez from comment #2)
> > What does -### show for the call to cc1 ? My commit r228094 to opts-common.c
> > should have fixed this.
>
> $ gcc -fdiagnostics-color=never a.c -###
> cc1.exe -quiet -D__USES_INITFINI__ a.c -quiet -dumpbase a.c -auxbase a -o
> /tmp/cclEySGP.s
To be honest, I don't have any clue why this is happening. This output seems to
happen before calling any code in opts-common.c as a result of the specs. But
why the specs will be touching -fdiagnostics-color=? I don't know much about
how the specs work.
If reverting the patch fixes the problem, please go ahead and just reopen the
bug fixed by it.