public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: "augustine.sterling@gmail.com" <augustine.sterling@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Marc Gauthier <marc@cadence.com>
Subject: Re: [PATCH 2/2] xtensa: use pre- and postincrement FP load/store when available
Date: Wed, 15 Oct 2014 04:34:00 -0000	[thread overview]
Message-ID: <CAMo8BfKfspVm6e-rTYGGR8rhRm3Bt1O3xk426X7GT01PcvoJzw@mail.gmail.com> (raw)
In-Reply-To: <CAGSvup8Vhdq-AxtdX2aYGEfUGbLb+0G3kAh408tRwMmB77ygZA@mail.gmail.com>

On Mon, Oct 13, 2014 at 8:04 PM, augustine.sterling@gmail.com
<augustine.sterling@gmail.com> wrote:
> On Sun, Oct 12, 2014 at 3:46 PM, Max Filippov <jcmvbkbc@gmail.com> wrote:
>> 2014-10-10  Max Filippov  <jcmvbkbc@gmail.com>
>>
>> gcc/
>>     * config/xtensa/xtensa.h (TARGET_HARD_FLOAT_POSTINC): new macro.
>>     * config/xtensa/xtensa.md (*lsiu, *ssiu): add dependency on
>>     !TARGET_HARD_FLOAT_POSTINC.
>>     (*lsip, *ssip): new instructions.
>
> Approved. Do you have write priviliges?

Applied to trunk. Thanks!

-- Max

  parent reply	other threads:[~2014-10-15  4:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-12 22:46 [PATCH 0/2] xtensa: fix floating-point parts of machine description Max Filippov
2014-10-12 22:46 ` [PATCH 1/2] xtensa: drop unimplemented floating point operations Max Filippov
2014-10-13 16:09   ` augustine.sterling
2014-10-15  4:23     ` Max Filippov
2014-10-12 23:19 ` [PATCH 2/2] xtensa: use pre- and postincrement FP load/store when available Max Filippov
2014-10-13 16:05   ` augustine.sterling
2014-10-14  0:16     ` Max Filippov
2014-10-15  4:34     ` Max Filippov [this message]
2014-10-13 16:04 ` [PATCH 0/2] xtensa: fix floating-point parts of machine description augustine.sterling
2014-10-13 22:43   ` Max Filippov

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=CAMo8BfKfspVm6e-rTYGGR8rhRm3Bt1O3xk426X7GT01PcvoJzw@mail.gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=augustine.sterling@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=marc@cadence.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).