public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>
To: Alex Coplan <alex.coplan@arm.com>, newlib@sourceware.org
Subject: Re: [PATCH] libgloss/aarch64: Add support for Armv8-R AArch64
Date: Tue, 29 Sep 2020 15:06:24 +0100	[thread overview]
Message-ID: <0bdab8d7-67ee-0d61-3e80-1b8365c41204@arm.com> (raw)
In-Reply-To: <20200918144327.7qgh64f57myg6njs@arm.com>

On 18/09/2020 15:43, Alex Coplan wrote:
> Hello,
> 
> This patch adds support for Armv8-R AArch64. We update the AArch64 CPU
> boot code to work on Armv8-R if __ARM_ARCH_PROFILE is set to 'R'.
> Armv8-R AArch64 has no EL3, so we don't set vbar_el3, and adjust the
> code to set up the MPU for Armv8-R.
> 
> We also add a specs file for use with Armv8-R AArch64 models.
> 
> Testing:
>  * Ran AArch64 GCC testsuite using --with-arch=armv8-r together with the
>    new specs file and boot code in an Armv8-R AArch64 model.
>  * Ran newlib testsuite, no regressions.
> 
> OK for master?
> 
> Thanks,
> Alex
> 
> ---
> 
> 2020-09-18  Alex Coplan  <alex.coplan@arm.com>
> 
> libgloss/ChangeLog:
> 
> 	* aarch64/Makefile.in: Install new specs file.
> 	* aarch64/cpu-init/Makefile.in: Also build boot code for Armv8-R.
> 	* aarch64/cpu-init/rdimon-aem-el3.S: Add support for Armv8-R.
> 	* aarch64/elf-aem-v8-r.specs: New.
> 

The main problem I see with this is that it assumes that the compiler
being used is *not* configured for a default CPU architecture of
ARMv8-r.  If it is, then the normal rdimon-aem-el3.o file will in fact
become the same as the v8-r version, which is not really what we want.

Perhaps, rather than hacking around the __ARM_ARCH_PROFILE setting you
should just set things up to build the file twice, but with a different
conventional pre-define set each time.

R.

  parent reply	other threads:[~2020-09-29 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 14:43 Alex Coplan
2020-09-22 12:42 ` Kyrylo Tkachov
2020-09-29 14:06 ` Richard Earnshaw (lists) [this message]
2020-09-29 16:27   ` Alex Coplan
2020-09-30 10:25     ` Richard Earnshaw (lists)
2020-09-30 13:25       ` UNSUBSCRIBE Brian Hawley

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=0bdab8d7-67ee-0d61-3e80-1b8365c41204@arm.com \
    --to=richard.earnshaw@arm.com \
    --cc=alex.coplan@arm.com \
    --cc=newlib@sourceware.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).