public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: gcc-patches@gcc.gnu.org,charles.baylis@linaro.org,Ramana.Radhakrishnan@arm.com,kyrylo.tkachov@arm.com
Cc: rearnsha@arm.com
Subject: Re: [PATCH 1/2] [ARM] Refactor costs calculation for MEM.
Date: Thu, 23 Feb 2017 07:46:00 -0000	[thread overview]
Message-ID: <A52BDA78-49BF-4C7C-8E51-7F8AC0EDEE77@gmail.com> (raw)
In-Reply-To: <1487696064-3233-2-git-send-email-charles.baylis@linaro.org>

On 21 February 2017 17:54:23 CET, charles.baylis@linaro.org wrote:
>From: Charles Baylis <charles.baylis@linaro.org>
>

>+/* Convert fron bytes to ints.  */

s/fron/from/

>+#define ARM_NUM_INTS(X) (((X) + UNITS_PER_WORD - 1) / UNITS_PER_WORD)
>+
>+
> /* RTX costs.  Make an estimate of the cost of executing the operation
>    X, which is contained with an operation with code OUTER_CODE.
>    SPEED_P indicates whether the cost desired is the performance cost,

s/contained with /contained within /
while you are at it.

thanks,

  reply	other threads:[~2017-02-23  7:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-21 16:54 [PATCH 0/2] [ARM] PR61551 addressing mode costs charles.baylis
2017-02-21 16:54 ` [PATCH 1/2] [ARM] Refactor costs calculation for MEM charles.baylis
2017-02-23  7:46   ` Bernhard Reutner-Fischer [this message]
2017-06-09 13:59   ` Richard Earnshaw (lists)
2017-08-25 18:16     ` Charles Baylis
2017-02-21 16:58 ` [PATCH 2/2] [ARM] Add table of costs for AAarch32 addressing modes charles.baylis
2017-06-09 14:13   ` Richard Earnshaw (lists)
2017-08-25 19:05     ` Charles Baylis
2017-08-25 19:10       ` Andrew Pinski
2017-05-12 15:53 ` [PATCH 0/2] [ARM] PR61551 addressing mode costs Charles Baylis

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=A52BDA78-49BF-4C7C-8E51-7F8AC0EDEE77@gmail.com \
    --to=rep.dot.nop@gmail.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=charles.baylis@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kyrylo.tkachov@arm.com \
    --cc=rearnsha@arm.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).