Hi Steve, > > Hi Steve, > > No we are using aarch64_be-*-* but this is the only one that popped up as a > failure which is why I didn't change the others. > But now I'm wondering why... I'll check the log file manually tomorrow to be > sure.
I've checked and the reason this didn't show up is because we don't run AArch64 big-endian cross linux tests by default and the baremetal builds don't support gomp. I'm happy to update them for you if you want though. Cheers, Tamar > > Cheers, > Tamar > ________________________________________ > From: Steve Ellcey <sell...@marvell.com> > Sent: Tuesday, January 22, 2019 10:34 PM > To: Tamar Christina; Richard Sandiford > Cc: gcc-patches@gcc.gnu.org; nd; christophe.l...@linaro.org > Subject: Re: [EXT] Re: [Patch 2/4][Aarch64] v2: Implement Aarch64 SIMD ABI > > On Mon, 2019-01-21 at 18:00 +0000, Tamar Christina wrote: > > > > > That would need to be aarch64*-*-* to include big-endian. Fixing > > > that here and in the other tests is OK under the obvious rule. > > > > Ah, true, I didn't look at the testcase. I tested the ILP32 case and > > committed the fix for both. > > > > Thanks, > > Tamar > > > > > > > > Adding && lp64 (as per Steve's patch below) is OK too if it works. > > > > > > Thanks, > > > Richard > > Thanks for fixing this test Tamar. I am going to change the others to use > 'aarch64*-*-*' instead of 'aarch64-*-*' since that seems to be the standard > method (though I see a few other tests that are not using > aarch64 instead of aarch64*). > > I guess that while you are testing big-endian the target triplet you are > using is > still aarch64-*-* and not aarch64be-*-*? Otherwise I would have expected > you to have more failures. > > Steve Ellcey > sell...@marvell.com