[Bug backends/27925] riscv backend only provides return value locations for code compiled for LP64D ABI

["mark at klomp dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=27925

Mark Wielaard <mark at klomp dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #13 from Mark Wielaard <mark at klomp dot org> ---
(In reply to William Cohen from comment #12)
> The patch for the retval handling has been submitted.

Thanks. I added a ChangeLog entry, made some (GNU) code style changes and
committed as:

commit 2e57301be1bbb9c34f8a59122ab500de46eb7acb (HEAD -> master)
Author: William Cohen <wcohen@redhat.com>
Date:   Wed Sep 29 14:56:15 2021 -0400

    RISC-V: PR27925 Add support for LP64 and LP64F ABIs return values

    The RISC-V Linux kernel is compiled without floating point (the LP64
    ABI) and elfutils could not obtain return value locations for
    functions in the kernel.  This issue was noticed when Systemtap
    generated RISC-V kernel modules for scripts that used $return target
    variables in function return probes. This patch adds the needed
    support to provide return value information for the LP64 and LP64F
    ABIs.

    Signed-off-by: William Cohen <wcohen@redhat.com>

>  As mentioned in
> comment #9 testing is not trivial.  Normal user-space executables are
> compiled with floating-point enabled and those executables work fine without
> the fixes.  The LP64 and LP64F ABIs don't have the need start or libraries
> to compile user-space tests.  Leaving the testsuite for later consideration.

OK. But even a testcase for the already working "normal" user-space would be
appreciated. And we might be able to create a kernel module as testcase.

-- 
You are receiving this mail because:
You are on the CC list for the bug.