public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/99933] New: gcc/brig/brigfrontend/brig-function.cc: 4 * possible performance problem ?
Date: Tue, 06 Apr 2021 11:13:28 +0000 [thread overview]
Message-ID: <bug-99933-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99933
Bug ID: 99933
Summary: gcc/brig/brigfrontend/brig-function.cc: 4 * possible
performance problem ?
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Static analyser cppcheck finds the following:
trunk.git/gcc/brig/brigfrontend/brig-function.cc:1063:11: performance: Passing
the result of c_str() to a function that takes std::string as argument no. 1 is
slow and redundant. [stlcstrParam]
trunk.git/gcc/brig/brigfrontend/brig-function.cc:1091:11: performance: Passing
the result of c_str() to a function that takes std::string as argument no. 1 is
slow and redundant. [stlcstrParam]
trunk.git/gcc/brig/brigfrontend/brig-function.cc:1108:11: performance: Passing
the result of c_str() to a function that takes std::string as argument no. 1 is
slow and redundant. [stlcstrParam]
trunk.git/gcc/brig/brigfrontend/brig-function.cc:1126:11: performance: Passing
the result of c_str() to a function that takes std::string as argument no. 1 is
slow and redundant. [stlcstrParam]
In the component field of the web page, there doesn't seem to be an entry
for brig.
next reply other threads:[~2021-04-06 11:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 11:13 dcb314 at hotmail dot com [this message]
2021-04-06 12:05 ` [Bug other/99933] " dcb314 at hotmail dot com
2021-04-06 13:51 ` marxin at gcc dot gnu.org
2021-05-13 12:17 ` marxin 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-99933-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).