public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Etienne Carriere" <etienne.carriere@linaro.org>
To: Sami Mujawar <sami.mujawar@arm.com>
Cc: devel@edk2.groups.io, Achin Gupta <achin.gupta@arm.com>,
	 Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Jiewen Yao <jiewen.yao@intel.com>,
	 Leif Lindholm <leif@nuviainc.com>,
	Sughosh Ganu <sughosh.ganu@linaro.org>,
	nd@arm.com
Subject: Re: [PATCH v3 5/5] StandaloneMmPkg: build for 32bit arm machines
Date: Wed, 19 May 2021 08:20:29 +0200	[thread overview]
Message-ID: <CAN5uoS_AKnBXThxSryTbx2XD9WRGtWam0Gbv=DFyYKegPBCiyQ@mail.gmail.com> (raw)
In-Reply-To: <a079b3b1-c591-3213-06d1-b736f18e03bd@arm.com>

Hello Sami,

Thanks for the catch. I missed that. My comment below.

On Tue, 18 May 2021 at 13:07, Sami Mujawar <sami.mujawar@arm.com> wrote:
>
> Hi Etienne,
>
> Please find my response inline marked [SAMI].
>
> Regards,
>
> Sami Mujawar
>
> On 17/05/2021 08:40 AM, Etienne Carriere wrote:
> > This change allows to build StandaloneMmPkg components for 32bit Arm
> > StandaloneMm firmware.
> >
> > This change mainly moves AArch64/ source files to Arm/ side directory
> > for several components:  StandaloneMmCpu, StandaloneMmCoreEntryPoint
> > and StandaloneMmMemLib. The source file is built for both 32b and 64b
> > Arm targets.
> > (snip)
> > --- a/StandaloneMmPkg/StandaloneMmPkg.dsc
> > +++ b/StandaloneMmPkg/StandaloneMmPkg.dsc
> > (snip)
> > @@ -131,7 +131,7 @@
> >   #                        module style (EDK or EDKII) specified in [Components] section.
> >   #
> >   ###################################################################################################
> > -[BuildOptions.AARCH64]
> > +[BuildOptions.AARCH64, BuildOptions.ARM]
> >   GCC:*_*_*_DLINK_FLAGS = -z common-page-size=0x1000 -march=armv8-a+nofp -mstrict-align
> [SAMI] Looks like I missed this in my previous review, sorry.
> Is '-march=armv8-axxx' correct here? or we need another ARM section with
> -march=armv7-a?
> Can you also check if '-mstrict-align' is right and if
> '-fno-stack-protector' is needed instead, please?
>
> I used the following setting from your edk2-platforms patch v1 4/4, file
> Platform/StandaloneMm/PlatformStandaloneMmPkg/PlatformStandaloneMmRpmb.dsc
> and was able to build on a Windows host PC using
> gcc-arm-9.2-2019.12-mingw-w64-i686-arm-none-eabi compiler.
>          [BuildOptions.ARM]
>          GCC:*_*_*_DLINK_FLAGS = -z common-page-size=0x1000 -march=armv7-a
>          GCC:*_*_*_CC_FLAGS = -fno-stack-protector
> [/SAMI]

You are right.
I saw that I build with these same directive but inherited from my
edk2-platforms platform that override these.
Indeed BuildOptions.ARM must be updated.
I am preparing a patch v4 series.

Regards,
Etienne


> >   GCC:*_*_*_CC_FLAGS = -mstrict-align
> >
>

  reply	other threads:[~2021-05-19  6:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  7:40 [PATCH v3 1/5] ArmPkg/IndustryStandard: 32b/64b agnostic FF-A, Mm SVC and Std SMC IDs Etienne Carriere
2021-05-17  7:40 ` [PATCH v3 2/5] ArmPkg: prepare 32bit ARM build of StandaloneMmPkg Etienne Carriere
2021-05-18 11:05   ` Sami Mujawar
2021-05-17  7:40 ` [PATCH v3 3/5] GenFv: Arm: support images entered in Thumb mode Etienne Carriere
2021-05-18 11:05   ` Sami Mujawar
2021-05-17  7:40 ` [PATCH v3 4/5] StandaloneMmPkg: fix pointer/int casts against 32bit architectures Etienne Carriere
2021-05-18 11:05   ` Sami Mujawar
2021-05-17  7:40 ` [PATCH v3 5/5] StandaloneMmPkg: build for 32bit arm machines Etienne Carriere
2021-05-18 11:07   ` Sami Mujawar
2021-05-19  6:20     ` Etienne Carriere [this message]
2021-05-18 11:04 ` [PATCH v3 1/5] ArmPkg/IndustryStandard: 32b/64b agnostic FF-A, Mm SVC and Std SMC IDs Sami Mujawar

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-list 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='CAN5uoS_AKnBXThxSryTbx2XD9WRGtWam0Gbv=DFyYKegPBCiyQ@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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