Hi Eric,

Yes, this is a problem that is pretty much guaranteed to happen given the
way the C ABI works in LLVM.  All of the test results
in BackendCABIOracleTests.cpp are specific to the details of the amd64 ABI.

The way that I had imagined this working was that either each testpoint has
a loop over the various supported ABI flavors (and checks output for each
flavor), or we have separate testpoints for each ABI
(e.g. TEST(BackendCABIOracleTests, X8664_RecursiveCall1) or equivalent. Or
even separate test files, depending on what's more convenient. It would be
nice if FcnTestHarness could be extended to accept a "target ABI"
parameter, maybe? Whatever you think is the best approach.

Thanks for taking care of this --

Than




On Fri, Oct 25, 2019 at 2:41 AM eric fang <eric.f...@arm.com> wrote:

> Hi Than,
>
> I'm porting the unit test cases of x86 to arm64. As the difference between
> x86 abi and arm64 abi, for the same go code snippet, the generated llvm IRs
> maybe different.
> How do you get the correct IR result of a unit test? Such as unit
> test TEST(BackendCABIOracleTests, RecursiveCall1). Is there any quick way?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-nuts+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/golang-nuts/bcd0ea2c-d1e3-43f7-88ea-0c8de78f96f6%40googlegroups.com
> <https://groups.google.com/d/msgid/golang-nuts/bcd0ea2c-d1e3-43f7-88ea-0c8de78f96f6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CA%2BUr55FciscRp%2BYPLo_PVBXQx1pF%2BMZdBrY3WT_U8%2B56-Sb13Q%40mail.gmail.com.

Reply via email to