From: "Ying Huang" <ying.huang@oss.cipunited.com>
To: <fweimer@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re:[PATCH v2] MIPS: Sync elf.h from binutils
Date: Tue, 16 May 2023 17:12:31 +0800 [thread overview]
Message-ID: <7518d9d2-138b-d58b-6d95-ef5250093bab@oss.cipunited.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
HI,
> >/+#define EF_MIPS_MACH 0x00FF0000 /* Machine variant if we know it. This field was invented at Cygnus, />/+ but it is hoped that other vendors will adopt it. If some standard />/+ is developed, this code should be changed to follow it. */ />/+#define E_MIPS_MACH_3900 0x00810000 /* Cygnus is choosing values between 80 and 9F; />/+ 00 - 7F should be left for a future standard; />/+ the rest are open. */ /
> Surely after around 25 years, these comments can be more precise?
OK, I would delete the comments.
>
> >/+/* Object attribute tags. */ />/+enum />/+{ />/+ /* 0-3 are generic. */ />/+ />/+ /* Floating-point ABI used by this object file. */ />/+ Tag_GNU_MIPS_ABI_FP = 4, />/+ />/+ /* MSA ABI used by this object file. */ />/+ Tag_GNU_MIPS_ABI_MSA = 8, />/+}; />/+ />/+/* Object attribute values. */ />/+enum />/+{ />/+ /* Values defined for Tag_GNU_MIPS_ABI_MSA. */ />/+ />/+ /* Not tagged or not using any ABIs affected by the differences. */ />/+ Val_GNU_MIPS_ABI_MSA_ANY = 0, />/+ />/+ /* Using 128-bit MSA. */ />/+ Val_GNU_MIPS_ABI_MSA_128 = 1, />/+}; /
> Any reason for using enum constants here, and not #define? I understand
> there is other MIPS precedent, but why continue in this direction?
>
> Thanks,
>
OK, I would change it to #define && submit PATCH v3.
Thanks,
Ying
next reply other threads:[~2023-05-16 9:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 9:12 Ying Huang [this message]
2023-06-01 9:17 ` [PATCH " Ying Huang
2023-06-01 9:21 ` Florian Weimer
2023-06-01 9:40 ` Ying Huang
2023-06-01 10:32 ` Florian Weimer
2023-06-01 10:46 ` 黄莺
2023-06-28 1:43 ` Ying Huang
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=7518d9d2-138b-d58b-6d95-ef5250093bab@oss.cipunited.com \
--to=ying.huang@oss.cipunited.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).