public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/105364] lto-wrapper generates URLs escape sequences despite -fdiagnostic-urls=never Date: Tue, 26 Apr 2022 13:47:11 +0000 [thread overview] Message-ID: <bug-105364-4-Tf2dg63xKK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105364-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105364 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>: https://gcc.gnu.org/g:cd4acb8cd9e45fd35664baa5b0a3150e479aae32 commit r12-8269-gcd4acb8cd9e45fd35664baa5b0a3150e479aae32 Author: Martin Liska <mliska@suse.cz> Date: Tue Apr 26 09:56:37 2022 +0200 lto: use diagnostics_context in print_lto_docs_link Properly parse OPT_fdiagnostics_urls_ and then initialize both urls and colors for global_dc. Doing that we would follow the configure option --with-documentation-root-url, -fdiagnostics-urls is respected. Plus we'll print colored warning and note messages. PR lto/105364 gcc/ChangeLog: * lto-wrapper.cc (print_lto_docs_link): Use global_dc. (run_gcc): Parse OPT_fdiagnostics_urls_. (main): Initialize global_dc.
next prev parent reply other threads:[~2022-04-26 13:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-24 15:30 [Bug plugins/105364] New: " wavexx at thregr dot org 2022-04-25 6:57 ` [Bug lto/105364] " rguenth at gcc dot gnu.org 2022-04-25 6:57 ` rguenth at gcc dot gnu.org 2022-04-25 12:54 ` marxin at gcc dot gnu.org 2022-04-26 13:47 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-26 13:49 ` marxin at gcc dot gnu.org 2022-04-29 10:11 ` wavexx at thregr dot org 2022-11-28 22:04 ` pinskia at gcc dot gnu.org
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=bug-105364-4-Tf2dg63xKK@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).