From: Suprateeka R Hegde <hegdesmailbox@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, gnu-gabi@sourceware.org
Subject: Re: RFC: Program Properties
Date: Fri, 01 Jan 2016 00:00:00 -0000 [thread overview]
Message-ID: <62be87c7-53c1-b4f4-4ad3-57683464ffdd@gmail.com> (raw)
In-Reply-To: <CAMe9rOqvWG-soQJCCOtVtRGjEWc6oF59t0J6iJHBZiY7R2rj1Q@mail.gmail.com>
On 12-Oct-2016 11:33 PM, H.J. Lu wrote:
> 1. Minimum ISAs. Executables and shared objects, which are optimized
> specifically to run on a particular processor, will not run on processors
> which don't support the same set of ISAs. Since x86 only has EM_IAMCU,
> EM_386 and EM_X86_64 ELF machine codes, run-time loader needs additional
> information to tell if an executable or a shared object is compatible
> with available ISAs.
Why cant the following be defined as processor specific e_flags (like
other processors do) in elf.h itself?
Instead of GNU_PROPERT_X86_*, why cant we have EF_X86_* (and adjust the
mechanism/logic of the proposal accordingly) ? That would make it
uniform at least as per elf.h.
X86, as a processor architecture, need not be tied to GNU?
> Integer value for the x86 instruction set support.
>
> #define GNU_PROPERTY_X86_ISA_1_486 (1U << 0)
> #define GNU_PROPERTY_X86_ISA_1_586 (1U << 1)
> #define GNU_PROPERTY_X86_ISA_1_686 (1U << 2)
> #define GNU_PROPERTY_X86_ISA_1_SSE (1U << 3)
> #define GNU_PROPERTY_X86_ISA_1_SSE2 (1U << 4)
> #define GNU_PROPERTY_X86_ISA_1_SSE3 (1U << 5)
> #define GNU_PROPERTY_X86_ISA_1_SSSE3 (1U << 6)
> #define GNU_PROPERTY_X86_ISA_1_SSE4_1 (1U << 7)
> #define GNU_PROPERTY_X86_ISA_1_SSE4_2 (1U << 8)
> #define GNU_PROPERTY_X86_ISA_1_AVX (1U << 9)
> #define GNU_PROPERTY_X86_ISA_1_AVX2 (1U << 10)
> #define GNU_PROPERTY_X86_ISA_1_AVX512F (1U << 11)
> #define GNU_PROPERTY_X86_ISA_1_AVX512CD (1U << 12)
> #define GNU_PROPERTY_X86_ISA_1_AVX512ER (1U << 13)
> #define GNU_PROPERTY_X86_ISA_1_AVX512PF (1U << 14)
> #define GNU_PROPERTY_X86_ISA_1_AVX512VL (1U << 15)
> #define GNU_PROPERTY_X86_ISA_1_AVX512DQ (1U << 16)
> #define GNU_PROPERTY_X86_ISA_1_AVX512BW (1U << 17)
--
Supra
next prev parent reply other threads:[~2016-10-13 6:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-01 0:00 H.J. Lu
2016-01-01 0:00 ` Suprateeka R Hegde [this message]
2016-01-01 0:00 ` Jose E. Marchesi
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Jose E. Marchesi
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` Joseph Myers
2016-01-01 0:00 ` Carlos O'Donell
2016-01-01 0:00 ` Maciej W. Rozycki
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Maciej W. Rozycki
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Nick Clifton
2016-01-01 0:00 ` H.J. Lu
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2016-01-01 0:00 H.J. Lu
2016-01-01 0:00 ` Suprateeka R Hegde
2016-01-01 0:00 H.J. Lu
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=62be87c7-53c1-b4f4-4ad3-57683464ffdd@gmail.com \
--to=hegdesmailbox@gmail.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@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).