From: Jeff Law <law@redhat.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: Richard Henderson <rth@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Denis Chertykov <chertykov@gmail.com>
Subject: Re: [RFC] Cleanup DW_CFA_GNU_args_size handling
Date: Wed, 03 Aug 2011 16:24:00 -0000 [thread overview]
Message-ID: <4E397638.40802@redhat.com> (raw)
In-Reply-To: <4E395612.8060806@gjlay.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/03/11 08:07, Georg-Johann Lay wrote:
> Georg-Johann Lay wrote:
>> Richard Henderson wrote:
>>> On 08/01/2011 11:42 AM, Georg-Johann Lay wrote:
>>>> Is there a specific reason not to define
>>>> ACCUMULATE_OUTGOING_ARGS on AVR?
>>> Yes. So that you can use PUSH. But as I said in PR49881, you
>>> probably want to provide -maccumulate-outgoing-args.
>>>
>>> I have a follow-up patch to the last one in that PR...
>>>
>>>
>>> r~
>>
>> PUSH is fine but what about POP?
>>
>> It's very expensive to pop several bytes, i.e. disabling IRQs,
>> loading and storing SP and the like. Usung store+displacement has
>> not this drawback and as I wrote, come code degradations you
>> explained in PR49881 are artifacts of PR46278, i.e. fake X
>> addressing.
>>
>> Johann
>>
>
> Tried this test case:
>
> #include <stdio.h>
>
> void foo () { printf ("%d %d %d", 1, 2, 3); printf ("%d %d %d", 3, 4,
> 5); printf ("%d %d %d", 1, 4, 5); }
>
> Attached the output: The compiler happily pushes onto the stack but
> pops only at the end of the function. So in a function with many such
> calls that would eat up great deal of RAM. It that what we want?
>
> RETURN_POPS_ARGS cannot help here.
Popping arguments is deferred until the accumulated size of the deferred
argument pops reaches a particular threshold or certain other conditions
are met (see NO_DEFER_POP).
I don't recall the parameters used to determine when the accumulated
size is large enough to force pops, but I'm sure you can find it with a
little searching in the GCC sources.
Ahhh, memories of the m68k...
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJOOXY4AAoJEBRtltQi2kC79VkH/Ar4NFKpU9mMXS+Pswz3vuOT
6Mv0pWGmuACBz7r69NZ9WNb2PQBXTJUp/vQJUbvKxIBFWmtEc6wRO1kYz3NuZ9FX
MRTXO+Mo3TWkFtzr5krq6d3r0CYVwa3ta/U/XNwvoo+XAUVkuYQgJi0C85yBQBwM
M9Q8nzWaJxAohSh+r6tOIBBdFG66YnfmZAYxLnsOaS5akm4tMuS6D5KFnJVJZbc7
btjNYzLvjCBXuekuHCyaq3HxpTTmhKWCFXuy55fUiOZGJJabPfTfbXlRaM5pGkPk
eo6gR9ydvMIt0RbYCSpqNy1RE+bOfeawqnoE/Mx86ZIzJZuLWOz+3K8UI5cINJ4=
=2Kgl
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-03 16:24 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 17:40 Richard Henderson
2011-08-01 18:43 ` Georg-Johann Lay
2011-08-01 18:47 ` Richard Henderson
2011-08-01 19:53 ` Denis Chertykov
2011-08-03 12:16 ` Georg-Johann Lay
2011-08-03 14:08 ` Georg-Johann Lay
2011-08-03 15:13 ` Richard Henderson
2011-08-03 15:49 ` Georg-Johann Lay
2011-08-03 15:53 ` Richard Henderson
2011-08-03 16:24 ` Jeff Law [this message]
2011-08-02 2:00 ` Richard Henderson
2011-08-02 22:32 ` Richard Henderson
2011-08-03 14:31 ` H.J. Lu
2011-08-03 17:39 ` H.J. Lu
2011-12-21 5:20 ` Jie Zhang
2011-08-03 14:07 ` Ulrich Weigand
2011-08-03 15:15 ` Richard Henderson
2011-08-03 17:01 ` Ulrich Weigand
2011-08-20 15:52 Gerald Pfeifer
2011-08-22 6:42 ` Eric Botcazou
2011-08-23 22:20 ` Richard Henderson
2011-08-24 6:44 ` Gerald Pfeifer
2011-08-24 7:38 ` Richard Henderson
2011-08-24 8:46 ` Gerald Pfeifer
2011-08-24 8:48 ` H.J. Lu
2011-08-24 17:38 ` Eric Botcazou
2011-09-04 18:39 ` Gerald Pfeifer
2011-09-09 10:01 ` Eric Botcazou
2011-09-09 19:07 ` Eric Botcazou
2011-09-09 20:02 ` H.J. Lu
2011-09-10 14:08 ` Eric Botcazou
2011-09-10 19:03 ` H.J. Lu
2011-09-11 2:35 ` Gerald Pfeifer
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=4E397638.40802@redhat.com \
--to=law@redhat.com \
--cc=avr@gjlay.de \
--cc=chertykov@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rth@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).