From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: [patch] Support C++11 rvalue (move constructor)
Date: Mon, 14 Oct 2013 17:57:00 -0000 [thread overview]
Message-ID: <20131014175747.GA9176@host2.jankratochvil.net> (raw)
In-Reply-To: <87fvs33kb7.fsf@fleche.redhat.com>
On Mon, 14 Oct 2013 18:10:20 +0200, Tom Tromey wrote:
> Jan> Therefore there is a KFAIL in the testcase for it. I do not think
> Jan> GDB needs to handle && differently - except for displaying &&
> Jan> instead of &.
>
> Is that also true for inferior calls?
> I didn't look.
GDB cannot call constructors so this is irrelevant now.
But it looks GCC really passes just a pointer (=like with lvalue reference).
> Maybe the size increase isn't that important.
I always thought the opposite is true.
Due to CU expansion with <tab> after some completions one easily gets to
1GB GDB and more (but IMO this is a bug <tab> should not expand CUs).
> Alternatively maybe it can be handled like qualifiers.
Interesting idea but I would rather go some more clean way.
> It seems reasonable to me -- an improvement, and not blocking any future
> improvements.
I will check it in in some days.
Thanks,
Jan
next prev parent reply other threads:[~2013-10-14 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-12 15:28 Jan Kratochvil
2013-10-14 16:10 ` Tom Tromey
2013-10-14 17:34 ` Jonathan Wakely
2013-10-14 17:57 ` Jan Kratochvil [this message]
2013-10-14 18:18 ` Tom Tromey
2013-10-16 13:32 ` Jan Kratochvil
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=20131014175747.GA9176@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jwakely.gcc@gmail.com \
--cc=tromey@redhat.com \
/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