Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@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 18:18:00 -0000	[thread overview]
Message-ID: <87hacj1zsk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20131014175747.GA9176@host2.jankratochvil.net> (Jan Kratochvil's	message of "Mon, 14 Oct 2013 19:57:47 +0200")

>> Is that also true for inferior calls?
>> I didn't look.

Jan> GDB cannot call constructors so this is irrelevant now.

I'm not sure constructors matter.  rvalue references affect overloading,
e.g.:

    #include <stdio.h>

    int ov(int &x) { return 0; }
    int ov(int &&x) { return 1; }

    int main() {
      int z = 23;
      printf ("%d %d\n", ov(z), ov(23));
    }


Tom> Maybe the size increase isn't that important.

Jan> I always thought the opposite is true.
Jan> Due to CU expansion with <tab> after some completions one easily gets to
Jan> 1GB GDB and more (but IMO this is a bug <tab> should not expand CUs).

I think what's missing is an idea of the amount that struct main_type
contributes.

My recollection is that I concluded that shrinking types wasn't
worthwhile.  However, it's worthwhile to redo the experiment, at least
if you plan to completely fix this problem.

Tom


  reply	other threads:[~2013-10-14 18:18 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
2013-10-14 18:18     ` Tom Tromey [this message]
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=87hacj1zsk.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=jwakely.gcc@gmail.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