Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] GDB testsuite: Suppress GCC's colored output
Date: Fri, 04 Aug 2017 13:00:00 -0000	[thread overview]
Message-ID: <864ltn32tw.fsf@gmail.com> (raw)
In-Reply-To: <3bec6ebd5ee77f9d5b134c1dda6b62ea@polymtl.ca> (Simon Marchi's	message of "Fri, 04 Aug 2017 14:19:44 +0200")

Simon Marchi <simon.marchi@polymtl.ca> writes:

> My gcc (5.4) doesn't recognize it:
>
> $ gcc -fno-color-diagnostics test.c
> gcc: error: unrecognized command line option ‘-fno-color-diagnostics’
>

Ah, sorry.  What I meant is -fdiagnostics-color=never.

> It knows about -fdiagnostics-color=never however, which clang seems to
> recognize as well.  It would be nice however not to restrict the
> compiler version used for testing just for this.  Can we write a small
> proc that checks if the compiler recognizes that flag and only include
> it if it does?

Yes, we can do that, but be careful on the recursive calls here.  We
want to pass -fdiagnostics-color=never to compiler during compilation,
but we need to check whether compiler understands this option or not.
When we test compiler, we may pass -fdiagnostics-color=never to compiler
to try to compile something again to see if compiler understands.

-- 
Yao (齐尧)


  reply	other threads:[~2017-08-04 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02 17:35 Andreas Arnez
2017-08-02 20:22 ` Simon Marchi
2017-08-03 11:13   ` Andreas Arnez
     [not found] ` <86h8xn3833.fsf@gmail.com>
2017-08-04 12:19   ` Simon Marchi
2017-08-04 13:00     ` Yao Qi [this message]
2017-08-08 18:29   ` Andreas Arnez
2017-08-09 10:01     ` Simon Marchi
2017-08-09 10:29     ` Yao Qi
2017-08-14 18:32       ` Andreas Arnez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864ltn32tw.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox