public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wavexx at thregr dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug plugins/105364] New: lto-wrapper generates URLs escape sequences despite -fdiagnostic-urls=never
Date: Sun, 24 Apr 2022 15:30:59 +0000 [thread overview]
Message-ID: <bug-105364-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105364
Bug ID: 105364
Summary: lto-wrapper generates URLs escape sequences despite
-fdiagnostic-urls=never
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: plugins
Assignee: unassigned at gcc dot gnu.org
Reporter: wavexx at thregr dot org
Target Milestone: ---
Warnings generated by lto-wrapper do not seem to check the current terminal
settings (TERM=dumb doesn't do anything useful) and/or even respect
-fdiagnostics-urls=never provided while linking:
gcc -Wl,--as-needed -fdiagnostics-urls=never -fPIE -pie -fuse-ld=mold -flto -o
spectrwm spectrwm.o linux.o -lX11-xcb -lX11 -lxcb-icccm -lxcb-keysyms
-lxcb-randr -lxcb-util -lxcb -lxcb-xinput -lxcb-xtest -lXcursor -lXft
lto-wrapper: warning: using serial compilation of 3 LTRANS jobs
lto-wrapper: note: see the
]8;;https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-flto‘-flto’
option documentation]8;; for more information
(note the inline escape ESC ] 8)
% gcc --version
gcc (Debian 12-20220319-1) 12.0.1 20220319 (experimental) [master
r12-7719-g8ca61ad148f]
next reply other threads:[~2022-04-24 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 15:30 wavexx at thregr dot org [this message]
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
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@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).