Thanks for the report. I'm going to pass this along to our toolchain team. Not sure when I'll get a fix, but hopefully soon.
On 3/22/21 3:18 PM, Daniel Mack wrote: > Hi Mark, > > Thanks again! > > On 3/14/21 1:16 AM, Mark Hatle wrote: >> On 3/13/21 2:15 PM, Daniel Mack wrote: > >>> Thanks a lot for the prompt reply! That explains. Now I'm wondering how >>> to best pass that flag, and to which part of the build exactly. Is there >>> any example how to do that in Yocto? >> >> Not a proper fix (that is still in progress upstream [kernel]), but you >> should >> be able to add this to arch/microblaze/Makefile >> >> Look for: head-y := arch/microblaze/kernel/head.o >> >> Right before that I added: >> >> KBUILD_CFLAGS += -fno-tree-loop-distribute-patterns > > That's what I tried first thing, but that alone didn't suffice > unfortunately. CONFIG_XILINX_MICROBLAZE0_USE_BARREL was set to 1 in my > kernel config to match the FPGA design which was made with > C_USE_BARREL=1. In order to get a booting kernel however, I had to > disable the barrel shifter in the kernel. > > After some more digging, it turned out that this downstream patch was > causing the issue: > > 0024-Patch-microblaze-Add-new-bit-field-instructions.patch > > That patch enables the bsefi and bsifi instructions which are only valid > for MicroBlaze version 10+, even though I selected v8.50 in > TUNE_FEATURES_tune-microblaze. > > Any idea? > > > Best regards, > Daniel > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4873): https://lists.yoctoproject.org/g/meta-xilinx/message/4873 Mute This Topic: https://lists.yoctoproject.org/mt/81285762/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
