public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rui314 at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29651] glibc can't handle IRELATIVE in .rel.plt only on ARM32 and PPC Date: Sat, 15 Oct 2022 02:06:27 +0000 [thread overview] Message-ID: <bug-29651-131-u6DG7FU9Ur@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29651-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29651 Rui Ueyama <rui314 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #5 from Rui Ueyama <rui314 at gmail dot com> --- I thought that the intention of glibc is to support that usage on all targets and somehow a few targets didn't support it. So, if it needs more work than just implementing it so that it will be usable someday in the future, I don't think it's worth to pursue. It's not that important anyway. I'll close this issue as "won't fix". -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2022-10-15 2:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-04 2:39 [Bug libc/29651] New: " rui314 at gmail dot com 2022-10-04 2:43 ` [Bug libc/29651] " rui314 at gmail dot com 2022-10-13 17:41 ` adhemerval.zanella at linaro dot org 2022-10-14 1:48 ` rui314 at gmail dot com 2022-10-14 12:16 ` adhemerval.zanella at linaro dot org 2022-10-14 13:40 ` adhemerval.zanella at linaro dot org 2022-10-15 2:06 ` rui314 at gmail dot com [this message]
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-29651-131-u6DG7FU9Ur@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).