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 c/94669] libcc1: 4 * minor performance problem
Date: Wed, 05 May 2021 06:10:59 +0000 [thread overview]
Message-ID: <bug-94669-4-TjWx3S4lef@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94669-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94669
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Tom Tromey <tromey@gcc.gnu.org>:
https://gcc.gnu.org/g:96deddca2e535d09db1d244a96a1efc20e24b673
commit r12-473-g96deddca2e535d09db1d244a96a1efc20e24b673
Author: Tom Tromey <tom@tromey.com>
Date: Tue May 4 15:26:58 2021 -0600
libcc1: avoid extra string copies
PR c/94669 points out that a couple of spots in libcc1 take a
std::string where a reference would do. This changes these spots to
take a const char *, to reduce the number of copies.
libcc1
PR c/94669
* compiler.hh (compiler_driver_filename): Take const char *.
(compiler_triplet_regexp): Likewise.
next prev parent reply other threads:[~2021-05-05 6:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:35 [Bug c/94669] New: libcc1/libcc1.cc; 2 " dcb314 at hotmail dot com
2020-04-20 12:13 ` [Bug c/94669] libcc1: 4 " dcb314 at hotmail dot com
2020-04-20 18:23 ` jan.kratochvil at redhat dot com
2020-04-20 18:33 ` dcb314 at hotmail dot com
2020-04-21 15:35 ` egallager at gcc dot gnu.org
2021-01-22 23:05 ` tromey at gcc dot gnu.org
2021-05-05 6:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-05 10:24 ` dcb314 at hotmail dot com
2022-01-05 18:22 ` tromey at gcc dot gnu.org
2022-01-05 18:26 ` redi 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-94669-4-TjWx3S4lef@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).