public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Renlin Li <renlin.li@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	 Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: [PING][PATCH][AARCH64]Add ACLE 2.0 predefined macros: __ARM_ALIGN_MAX_PWR and __ARM_ALIGN_MAX_STACK_PWR
Date: Tue, 28 Apr 2015 16:01:00 -0000	[thread overview]
Message-ID: <553FAC6C.4060705@arm.com> (raw)
In-Reply-To: <54900732.4010604@arm.com>

Ping~

Regards,
Renlin Li

On 16/12/14 10:19, Renlin Li wrote:
> Hi all,
>
> This is a simple patch to add another two ACLE 2.0 predefined macros
> into aarch64 backend.
> They are __ARM_ALIGN_MAX_PWR and __ARM_ALIGN_MAX_STACK_PWR. Currently,
> those two values are hard-wired to 16.
>
> The following clauses from ACLE 2.0 documentation indicate the meaning
> of those two macros:
>
> The macro __ARM_ALIGN_MAX_STACK_PWR indicates (as the exponent of a
> power of 2) the maximum available stack alignment.
> The macro __ARM_ALIGN_MAX_PWR indicates (as the exponent of a power of
> 2) the maximum available alignment of static data.
>
> aarch64-none-elf target is tested on on the model. No new regression.
>
> Is it Okay for trunk?
>
> Regards,
> Renlin Li
>
> gcc/ChangeLog
>
> 2014-12-16  Renlin Li  <renlin.li@arm.com>
>
>           * config/aarch64/aarch64.h(TARGET_CPU_CPP_BUILTINS): Define
> __ARM_ALIGN_MAX_PWR
>           and __ARM_ALIGN_MAX_STACK_PWR.

  reply	other threads:[~2015-04-28 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 10:24 [PATCH][AARCH64]Add " Renlin Li
2015-04-28 16:01 ` Renlin Li [this message]
2015-04-28 17:04 ` Marcus Shawcroft
2015-04-29  1:25 ` Andrew Pinski
2015-04-29 11:14   ` Marcus Shawcroft
2015-06-04 13:59     ` Renlin Li
2015-06-11 10:56       ` Marcus Shawcroft

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=553FAC6C.4060705@arm.com \
    --to=renlin.li@arm.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --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).