public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Michael Zimmermann <sigmaepsilon92@gmail.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	"Cohen, Eugene" <eugene@hp.com>
Subject: Re: [PATCH 1/3] ArmPkg/ArmSoftFloatLib: disable LTO build for GCC
Date: Sun, 7 Aug 2016 11:28:05 +0200	[thread overview]
Message-ID: <CAN9vWDLCiGhaKXkUC89N=FJT_=RiBumGxNNBkhxRN+w-Xs+0GQ@mail.gmail.com> (raw)
In-Reply-To: <CAN9vWD+Wthg1snnJx382=Ue9PC5tW6Nr3VWAPzihVaqyb5wEPg@mail.gmail.com>

Hi,

I researched a little bit on this topic and it seems that you have to add
fuse-linker-plugin to the build options to enable lto plugins.

I did that and unfortunately it had no effect. After running gcc through
strace I could see that liblto_plugin.so does get loaded from the
cross-toolchains libexec directory though.

Does that mean that the toolchain I use (GCC5 from releases.linaro.org and
GCC6 from git.linaro.org) generates lto objects which it can't process with
the shipped plugin?

btw, if I compile using my hosts native GCC(x64) but for IA32 I get lto
errors even for MdePkg. It looks like the fno-lto option is a very bad
workaround and can break any time using specific configurations.

Thanks
Michael

On Sat, Aug 6, 2016 at 4:53 PM, Michael Zimmermann <sigmaepsilon92@gmail.com
> wrote:

> not sure since I only tested it for ARM this time.
> these are the failing objects:
> SoftFloat:
> ld: __aeabi_dcmpeq.obj: plugin needed to handle lto object
> ld: __aeabi_fcmpeq.obj: plugin needed to handle lto object
> ld: __aeabi_dcmpge.obj: plugin needed to handle lto object
> ld: __aeabi_fcmpge.obj: plugin needed to handle lto object
> ld: __aeabi_dcmpgt.obj: plugin needed to handle lto object
> ld: __aeabi_fcmpgt.obj: plugin needed to handle lto object
> ld: __aeabi_dcmple.obj: plugin needed to handle lto object
> ld: __aeabi_fcmple.obj: plugin needed to handle lto object
> ld: __aeabi_dcmplt.obj: plugin needed to handle lto object
> ld: __aeabi_fcmplt.obj: plugin needed to handle lto object
>
> LibC:
> ld: fixunsdfsi.obj: plugin needed to handle lto object
> ld: fixunssfsi.obj: plugin needed to handle lto object
> ld: floatunsidf.obj: plugin needed to handle lto object
> ld: floatunsisf.obj: plugin needed to handle lto object
>
> Thanks
> Michael
>
> On Sat, Aug 6, 2016 at 4:42 PM, Ard Biesheuvel <ard.biesheuvel@linaro.org>
> wrote:
>
>> On 6 August 2016 at 16:18, Michael Zimmermann <sigmaepsilon92@gmail.com>
>> wrote:
>> > StdLib/LibC/Softfloat/Softfloat.inf and StdLib/LibC/LibC.inf need this
>> flags
>> > too.
>> >
>>
>> Just for ARM?
>>
>
>


  reply	other threads:[~2016-08-07  9:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 14:42 [PATCH 0/3] Build fixes for ARM/OpenSSL Ard Biesheuvel
2016-08-04 14:42 ` [PATCH 1/3] ArmPkg/ArmSoftFloatLib: disable LTO build for GCC Ard Biesheuvel
2016-08-06 14:18   ` Michael Zimmermann
2016-08-06 14:42     ` Ard Biesheuvel
2016-08-06 14:53       ` Michael Zimmermann
2016-08-07  9:28         ` Michael Zimmermann [this message]
2016-08-07 10:29           ` Ard Biesheuvel
2016-08-04 14:42 ` [PATCH 2/3] ArmPkg/CompilerIntrinsicsLib: make the default memset() weak Ard Biesheuvel
2016-08-04 14:42 ` [PATCH 3/3] BaseTools GCC/ARM: add -fno-builtin to CC flags Ard Biesheuvel
2016-08-04 16:01   ` Michael Zimmermann
2016-08-05 14:34     ` Ard Biesheuvel
2016-08-05 14:26   ` Gao, Liming
2016-08-05 14:33     ` Ard Biesheuvel
2016-08-05 12:53 ` [PATCH 0/3] Build fixes for ARM/OpenSSL Leif Lindholm

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='CAN9vWDLCiGhaKXkUC89N=FJT_=RiBumGxNNBkhxRN+w-Xs+0GQ@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