Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: simark@simark.ca (Simon Marchi)
Cc: brobecker@adacore.com (Joel Brobecker), gdb-patches@sourceware.org
Subject: [pushed] Re: [RFC][08/19] Target FP: Use target format throughout expression parsing
Date: Wed, 25 Oct 2017 13:35:00 -0000	[thread overview]
Message-ID: <20171025133524.AB565D807F1@oc3748833570.ibm.com> (raw)
In-Reply-To: <e96ca6af-7d12-a820-080f-215a2bb90b3f@simark.ca> from "Simon Marchi" at Oct 09, 2017 05:14:53 PM

> On 2017-10-09 02:12 PM, Joel Brobecker wrote:
> > One C++ thing I did notice but forgot to report...
> > 
> >> +floatformat_from_string (const struct floatformat *fmt, gdb_byte *out,
> >> +			 std::string in)
> > 
> > Again, to be double-checked, but I think you want to pass the argument
> > by reference in this case. Otherwise, you may end up having an overhead
> > with might not be necessary due to the creation of a copy of the string
> > being passed as argument here.
> > 
> 
> Indeed, it's good practice to pass constant strings (or other objects) as
> const references (const std::string &in).

I've now pushed this patch (using the const reference as suggested).

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU/Linux compilers and toolchain
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2017-10-25 13:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-05 18:21 Ulrich Weigand
2017-10-09 16:07 ` Joel Brobecker
2017-10-09 16:59   ` Ulrich Weigand
2017-10-09 18:12 ` Joel Brobecker
2017-10-09 21:14   ` Simon Marchi
2017-10-25 13:35     ` Ulrich Weigand [this message]
2017-11-03 12:33       ` [pushed] " Yao Qi
2017-11-03 13:45         ` Ulrich Weigand
2017-11-03 15:00           ` Yao Qi
2017-11-03 15:11             ` Ulrich Weigand

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=20171025133524.AB565D807F1@oc3748833570.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simark@simark.ca \
    /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