From: Siva Chandra <sivachandra@google.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v4] Make chained function calls in expressions work
Date: Tue, 04 Nov 2014 15:08:00 -0000 [thread overview]
Message-ID: <CAGyQ6gw_ZkdHi-fP5tvKmBGhi9VgYK5eYZSFyhX6HSvZ0sUGcQ@mail.gmail.com> (raw)
In-Reply-To: <201411041343.sA4DhRje024520@d06av02.portsmouth.uk.ibm.com>
On Tue, Nov 4, 2014 at 5:43 AM, Ulrich Weigand <uweigand@de.ibm.com> wrote:
> Well, that's true. For simple structs, we would have to create a
> temporary at the point of call when using a reference; we discussed
> adding this anyway (it's necessary for scalars as well) ...
I agree for scalars, but is it worth the effort to make this check for
structs/unions? Consider this example:
struct Simpler
{
char c;
char getc ();
};
struct Simple
{
Simpler a, b;
};
Simple
make_simple ()
{
Simple s;
s.a.c = 'a';
s.b.c = 'b';
return s;
}
Simple does not have any methods, but Simpler has. The ABI returns
objects of Simple type in register. However, one could have an
expression like this: make_simple().a.geta() which is equivalent to
f().g().
next prev parent reply other threads:[~2014-11-04 15:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-25 14:24 Siva Chandra
2014-11-03 14:35 ` Siva Chandra
2014-11-03 14:43 ` Ulrich Weigand
2014-11-03 19:55 ` Siva Chandra
2014-11-03 21:22 ` Siva Chandra
2014-11-04 13:43 ` Ulrich Weigand
2014-11-04 15:08 ` Siva Chandra [this message]
2014-11-04 15:40 ` Ulrich Weigand
2014-11-04 13:38 ` Ulrich Weigand
2014-11-04 14:26 ` Siva Chandra
2014-11-04 14:59 ` Ulrich Weigand
2014-11-04 15:23 ` Siva Chandra
2014-11-04 15:40 ` Ulrich Weigand
2014-11-11 14:55 ` Siva Chandra
2014-11-11 15:00 ` Siva Chandra
2014-11-11 15:21 ` Ulrich Weigand
2014-11-11 17:05 ` Siva Chandra
2014-11-12 16:08 ` Doug Evans
2014-11-12 17:29 ` Doug Evans
2014-11-13 3:00 ` Siva Chandra
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=CAGyQ6gw_ZkdHi-fP5tvKmBGhi9VgYK5eYZSFyhX6HSvZ0sUGcQ@mail.gmail.com \
--to=sivachandra@google.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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