From: Andreas Schwab <schwab@linux-m68k.org>
To: YunQiang Su via Libc-alpha <libc-alpha@sourceware.org>
Cc: binutils <binutils@sourceware.org>, YunQiang Su <wzssyqa@gmail.com>
Subject: Re: The definition of ELF64_MIPS_R_TYPE is ambiguous
Date: Sun, 23 Jul 2023 08:51:55 +0200 [thread overview]
Message-ID: <87fs5fjf1w.fsf@linux-m68k.org> (raw)
In-Reply-To: <CAKcpw6UjNkw8Z6m0=_w1NhWpap1WhjrVUzyRKc+J4bynB3zhcA@mail.gmail.com> (YunQiang Su via Libc-alpha's message of "Sun, 23 Jul 2023 12:52:18 +0800")
On Jul 23 2023, YunQiang Su via Libc-alpha wrote:
> I think that we should sync all of them to protect people from confusion.
> We are lucky enough that ELF64_MIPS_R_TYPE is not used widely by normal APPs.
> So it gives us the chance to make it sync between projects.
Is the macro defined by the ELF psABI?
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2023-07-23 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-23 4:52 YunQiang Su
2023-07-23 6:51 ` Andreas Schwab [this message]
2023-07-23 7:11 ` YunQiang Su
2023-07-23 7:18 ` Andreas Schwab
2023-08-07 11:09 ` Maciej W. Rozycki
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=87fs5fjf1w.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=wzssyqa@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).