From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [PATCH] backends (*_return_value_location): call dwarf_peeled_die_type
Date: Fri, 20 Jun 2014 23:40:42 +0200 [thread overview]
Message-ID: <1403300442.6147.12.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: ba9e5156207e3c2bb85adc747376e774af3c0df6.1403298635.git.pmachata@redhat.com
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Fri, 2014-06-20 at 23:15 +0200, Petr Machata wrote:
> ... instead of inlining equivalent code.
I didn't know we had that already. I was just contemplating whether to
add something like that. It also gets rid of the DW_TAG_mutable_type
issue (and in a nicer way than I did).
> +2014-06-20 Petr Machata <pmachata@redhat.com>
> +
> + * alpha_retval.c (alpha_return_value_location): Call
> + dwarf_peeled_die_type instead of inlining equivalent code.
> + * arm_retval.c (arm_return_value_location): Likewise.
> + * i386_retval.c (i386_return_value_location): Likewise.
> + * ia64_retval.c (ia64_return_value_location): Likewise.
> + * ppc64_retval.c (ppc64_return_value_location): Likewise.
> + * ppc_retval.c (ppc_return_value_location): Likewise.
> + * s390_retval.c (s390_return_value_location): Likewise.
> + * sh_retval.c (sh_return_value_location): Likewise.
> + * sparc_retval.c (sparc_return_value_location): Likewise.
> + * tilegx_retval.c (tilegx_return_value_location): Likewise.
> + * x86_64_retval.c (x86_64_return_value_location): Likewise.
Looks good. I'll rebase and push my 'Remove non-existing
DW_TAG_mutable_type' patch after this goes in.
Thanks,
Mark
next reply other threads:[~2014-06-20 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 21:40 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-20 22:12 Petr Machata
2014-06-20 21:15 Petr Machata
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=1403300442.6147.12.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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).