public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Youling Tang <tangyouling@loongson.cn>
To: elfutils-devel@sourceware.org, Mark Wielaard mark@klomp.org
Cc: Hengqi Chen <hengqi.chen@gmail.com>, Liwei Ge <geliwei@openanolis.org>
Subject: [PATCH 0/5] Improve LoongArch support
Date: Fri,  7 Apr 2023 10:59:23 +0800	[thread overview]
Message-ID: <1680836368-5373-1-git-send-email-tangyouling@loongson.cn> (raw)

Test Environment (New Toolchain):
 $ cat /etc/os-release
 NAME="My GNU/Linux System for LoongArch64"
 VERSION="6.0"
 ID=CLFS4LA64
 PRETTY_NAME="My GNU/Linux System for LoongArch64 6.0"

 $ gcc -v
 gcc version 13.0.0 20220919 (experimental) (GCC) 

Test Results:
 ============================================================================
 Testsuite summary for elfutils 0.189
 ============================================================================
 # TOTAL: 238
 # PASS:  234
 # SKIP:  4
 # XFAIL: 0
 # FAIL:  0
 # XPASS: 0
 # ERROR: 0
 ============================================================================


Youling Tang (5):
  backends: Add abi_cfi and register_info callbacks for LoongArch
  backends: Add set_initial_registers_tid callback for  LoongArch
  backends: Add initial return value location support for LoongArch
  backends: Add frame pointer unwinding for LoongArch
  backends: Add core_note callback for LoongArch

 backends/ChangeLog            |  33 +++++-
 backends/Makefile.am          |   4 +-
 backends/loongarch_cfi.c      |  83 ++++++++++++++
 backends/loongarch_corenote.c | 114 +++++++++++++++++++
 backends/loongarch_init.c     |  10 ++
 backends/loongarch_initreg.c  |  91 +++++++++++++++
 backends/loongarch_regs.c     | 141 ++++++++++++++++++++++++
 backends/loongarch_retval.c   | 202 ++++++++++++++++++++++++++++++++++
 backends/loongarch_unwind.c   |  84 ++++++++++++++
 9 files changed, 760 insertions(+), 2 deletions(-)
 create mode 100644 backends/loongarch_cfi.c
 create mode 100644 backends/loongarch_corenote.c
 create mode 100644 backends/loongarch_initreg.c
 create mode 100644 backends/loongarch_regs.c
 create mode 100644 backends/loongarch_retval.c
 create mode 100644 backends/loongarch_unwind.c

-- 
2.37.1


             reply	other threads:[~2023-04-07  2:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07  2:59 Youling Tang [this message]
2023-04-07  2:59 ` [PATCH 1/5] backends: Add abi_cfi and register_info callbacks for LoongArch Youling Tang
2023-05-08 19:48   ` Mark Wielaard
2023-04-07  2:59 ` [PATCH 2/5] backends: Add set_initial_registers_tid callback " Youling Tang
2023-05-08 19:57   ` Mark Wielaard
2023-05-09  1:32     ` Youling Tang
2023-05-09  1:38       ` Youling Tang
2023-05-09  9:57       ` Mark Wielaard
2023-04-07  2:59 ` [PATCH 3/5] backends: Add initial return value location support " Youling Tang
2023-05-08 20:04   ` Mark Wielaard
2023-04-07  2:59 ` [PATCH 4/5] backends: Add frame pointer unwinding " Youling Tang
2023-05-08 20:06   ` Mark Wielaard
2023-04-07  2:59 ` [PATCH 5/5] backends: Add core_note callback " Youling Tang
2023-05-08 20:15   ` Mark Wielaard

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=1680836368-5373-1-git-send-email-tangyouling@loongson.cn \
    --to=tangyouling@loongson.cn \
    --cc=elfutils-devel@sourceware.org \
    --cc=geliwei@openanolis.org \
    --cc=hengqi.chen@gmail.com \
    /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).