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: "EngyCZ at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 02 Nov 2015 14:38:02 +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 #5 from JiÅÃ Engelthaler <EngyCZ at gmail dot com> ---
(In reply to Manuel LÃpez-IbÃÃez from comment #4)
> (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.
I have tested GCC with reverted r228094 and there is not problem reported by
this bug.
I'm asking someone with rights to reopen the bug 67640 and link it to this one.