public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31151] [RISC-V] missing support for profile/audit PLT setup Date: Sat, 30 Dec 2023 10:00:32 +0000 [thread overview] Message-ID: <bug-31151-131-d4J2Gmas2N@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31151-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31151 --- Comment #3 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aurelien Jarno <aurel32@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6b32696116e0097f5dd578ec087bcbef483f2a07 commit 6b32696116e0097f5dd578ec087bcbef483f2a07 Author: Aurelien Jarno <aurelien@aurel32.net> Date: Sat Dec 30 11:00:10 2023 +0100 RISC-V: Add support for dl_runtime_profile (BZ #31151) Code is mostly inspired from the LoongArch one, which has a similar ABI, with minor changes to support riscv32 and register differences. This fixes elf/tst-sprof-basic. This also fixes elf/tst-audit1, elf/tst-audit2 and elf/tst-audit8 with recent binutils snapshots when --enable-bind-now is used. Resolves: BZ #31151 Acked-by: Palmer Dabbelt <palmer@rivosinc.com> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-12-30 10:00 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 17:45 [Bug libc/31151] New: [riscv64] elf/tst-audit{1,2,8} failures with --enable-bind-now and recent binutils aurelien at aurel32 dot net 2023-12-12 23:45 ` [Bug libc/31151] " sam at gentoo dot org 2023-12-13 12:43 ` schwab@linux-m68k.org 2023-12-13 15:16 ` [Bug libc/31151] [RISC-V] missing support for profile/audit PLT setup schwab@linux-m68k.org 2023-12-13 18:02 ` aurelien at aurel32 dot net 2023-12-30 10:00 ` cvs-commit at gcc dot gnu.org [this message] 2023-12-30 10:02 ` aurelien at aurel32 dot net
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-31151-131-d4J2Gmas2N@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).