public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Denis Chertykov <chertykov@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch,avr] Fix PR60300: Minor prologue improvement.
Date: Tue, 22 Nov 2016 18:23:00 -0000	[thread overview]
Message-ID: <CADOs=zZ3WMUe4y+XVfZkAM=xGtBRpaCNABxs7j137QieQMGJ8w@mail.gmail.com> (raw)
In-Reply-To: <e112ba96-8ef6-f3d8-2b9a-f1f93fdfca27@gjlay.de>

2016-11-22 15:41 GMT+03:00 Georg-Johann Lay <avr@gjlay.de>:
> This patch is a minor improvement of prologue length.  It now allows frame
> sizes of up to 11 to be allocated by RCALL + PUSH 0 sequences but limits the
> number of RCALLs to 3.
>
> The PR has some discussion on size vs. speed consideration w.r. to using
> RCALL in prologues, and following that I picked the rather arbitrary upper
> bound of 3 RCALLs.  The prior maximal frame size opt to such sequences was 6
> which also never produced more than 3 RCALLs.
>
> Ok for trunk?
>
>
> Johann
>
> gcc/
>         PR target/60300
>         * config/avr/constraints.md (Csp): Widen range to [-11..6].
>         * config/avr/avr.c (avr_prologue_setup_frame): Limit number
>         of RCALLs in prologue to 3.

Approved.

      reply	other threads:[~2016-11-22 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 12:42 Georg-Johann Lay
2016-11-22 18:23 ` Denis Chertykov [this message]

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='CADOs=zZ3WMUe4y+XVfZkAM=xGtBRpaCNABxs7j137QieQMGJ8w@mail.gmail.com' \
    --to=chertykov@gmail.com \
    --cc=avr@gjlay.de \
    --cc=gcc-patches@gcc.gnu.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).