public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug backends/27925] riscv backend only provides return value locations for code compiled for LP64D ABI
Date: Wed, 29 Sep 2021 13:43:05 +0000	[thread overview]
Message-ID: <bug-27925-10460-BBlpBYmhRw@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27925-10460@http.sourceware.org/bugzilla/>

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

--- Comment #10 from Mark Wielaard <mark at klomp dot org> ---
(In reply to Jim Wilson from comment #9)
> The patch looks OK to me.

So I like to include it. Will, could you sent the patch as a git commit (see
CONTRIBUTING) to the elfutils-devel list?

And if at all possible could someone generate some testcases? See Comment #6:

  There is tests/funcretval_test.c if you compile that
  (or a subset that doesn't return floating point values)
  as described in tests/run-funcretval.sh then we can
  construct a user space testcase.

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

  parent reply	other threads:[~2021-09-29 13:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27 18:58 [Bug backends/27925] New: " wcohen at redhat dot com
2021-09-18 21:18 ` [Bug backends/27925] " wcohen at redhat dot com
2021-09-19 10:30 ` mark at klomp dot org
2021-09-19 16:45 ` wilson at gcc dot gnu.org
2021-09-19 23:22 ` wcohen at redhat dot com
2021-09-20  2:29 ` wilson at gcc dot gnu.org
2021-09-20  7:42 ` mark at klomp dot org
2021-09-23  3:26 ` wcohen at redhat dot com
2021-09-23 14:22 ` wilson at gcc dot gnu.org
2021-09-23 14:30 ` wilson at gcc dot gnu.org
2021-09-29 13:43 ` mark at klomp dot org [this message]
2021-09-29 17:02 ` wilson at gcc dot gnu.org
2021-09-29 20:13 ` wcohen at redhat dot com
2021-09-29 22:14 ` mark at klomp dot org

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-all 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=bug-27925-10460-BBlpBYmhRw@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).