Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>, gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH] GDB testsuite: Re-enable -fdiagnostics-color=never
Date: Thu, 18 Jan 2018 18:35:00 -0000	[thread overview]
Message-ID: <7f9604a4-edef-709c-ed8a-d22b0cc4be0a@redhat.com> (raw)
In-Reply-To: <m3y3kv10st.fsf@oc1027705133.ibm.com>

On 01/18/2018 06:25 PM, Andreas Arnez wrote:
> In August 2017 the GDB test suite was changed to always add the compile
> option "-fdiagnostics-color=never", see:
> 
>   https://sourceware.org/ml/gdb-patches/2017-08/msg00150.html
> 
> Since this option is not understood by rustc, a commit from 09/2017
> dropped its use in that case:
> 
>   https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=5eb5f850
>   ("Don't use -fdiagnostics-color=never for rustc")
> 
> But that change goes overboard and stops using the option for other
> languages as well.  Thus compiler diagnostics written into gdb.log may
> contain colored output again.  This is fixed.
> 
> gdb/testsuite/ChangeLog:
> 
> 	* lib/gdb.exp (gdb_compile): Re-enable use of
> 	universal_compile_options for languages other than Rust.

OK.  Looks obvious to me.

Thanks,
Pedro Alves


  reply	other threads:[~2018-01-18 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 18:26 Andreas Arnez
2018-01-18 18:35 ` Pedro Alves [this message]
2018-01-18 18:44   ` 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=7f9604a4-edef-709c-ed8a-d22b0cc4be0a@redhat.com \
    --to=palves@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.com \
    /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