public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jan Beulich <jbeulich@suse.com>,
	Florian Weimer <fweimer@redhat.com>,
	GCC Development <gcc@gcc.gnu.org>,
	GNU C Library <libc-alpha@sourceware.org>,
	Tom Stellard <tstellar@redhat.com>,
	"Mallappa, Premachandra" <Premachandra.Mallappa@amd.com>,
	x86-64-abi <x86-64-abi@googlegroups.com>,
	llvm-dev@lists.llvm.org
Subject: Re: New x86-64 micro-architecture levels
Date: Mon, 13 Jul 2020 15:53:27 +0200	[thread overview]
Message-ID: <20200713135327.GK2363@tucnak> (raw)
In-Reply-To: <CAMe9rOqrk21vfxKD3Xw=ki-Y--xJ_kcUTc1ivUBythKwWsnJJg@mail.gmail.com>

On Mon, Jul 13, 2020 at 06:31:31AM -0700, H.J. Lu via Gcc wrote:
> > > H.J. has patches for ELF program properties.  I think
> > > GNU_PROPERTY_X86_ISA_1_NEEDED would convey this information.  This
> > > proposal and the glibc patches are independent of that.
> >
> > From (partly just halfway) recent discussions with H.J. I gained
> > the understanding that the piece we're aiming at getting to work
> > properly is the recording of GNU_PROPERTY_X86_FEATURE_2_*, not
> > so much GNU_PROPERTY_X86_ISA_1_*. If the ISA one is to be used as
> > a basis here, a lot of new flags will need adding (and properly
> > setting) first, I think.
> >
> 
> We can update GNU_PROPERTY_X86_ISA_1_* as needed.

I am not really sure such properties are a good idea, it will be a
maintainability nightmare (as it is on other OSes like Solaris).
Think about function multiversioning, target attribute for just some
functions, #pragma omp declare simd.  How do you differentiate between
using those on carefully written code that handles cpuid detection itself or
uses compiler support for that, where we do not want to mark the objects in
any way, they should work just fine even on K8, and cases where users want
something like that?

E.g. look for -mclear-hwcap stuff needed for Solaris because of that.

	Jakub


  reply	other threads:[~2020-07-13 13:53 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 17:30 Florian Weimer
2020-07-10 19:14 ` Joseph Myers
2020-07-13  7:55   ` Florian Weimer
2020-07-10 21:42 ` H.J. Lu
2020-07-13  6:23   ` Richard Biener
2020-07-13  7:40     ` Florian Weimer
2020-07-13  7:47       ` Jan Beulich
2020-07-13 13:31         ` H.J. Lu
2020-07-13 13:53           ` Jakub Jelinek [this message]
2020-07-13  8:57       ` Richard Biener
2020-07-13  6:49   ` Florian Weimer
2020-07-13 13:30     ` H.J. Lu
2020-07-11  7:40 ` Allan Sandfeld Jensen
2020-07-13  6:58   ` Florian Weimer
2020-07-15 14:38 ` Mark Wielaard
2020-07-15 14:45   ` H.J. Lu
2020-07-15 14:56   ` Florian Weimer
2020-07-21 16:05 ` Mallappa, Premachandra
2020-07-21 18:04   ` Florian Weimer
2020-07-22  1:31     ` Dongsheng Song
2020-07-22  8:44       ` Florian Weimer
2020-07-22  9:26         ` Richard Biener
2020-07-22 10:16           ` Florian Weimer
2020-07-22 13:50             ` Richard Biener
2020-07-22 14:21               ` H.J. Lu
2020-07-31 13:06           ` Carlos O'Donell
2020-07-22  7:48     ` Jan Beulich
2020-07-22 10:34       ` Florian Weimer
2020-07-22 11:41         ` Jan Beulich
2020-07-31 13:20         ` Carlos O'Donell
2020-07-22 16:45     ` Mallappa, Premachandra
2020-07-23 12:44       ` Michael Matz
2020-07-23 13:21         ` H.J. Lu
2020-07-28 15:54       ` Florian Weimer

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=20200713135327.GK2363@tucnak \
    --to=jakub@redhat.com \
    --cc=Premachandra.Mallappa@amd.com \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jbeulich@suse.com \
    --cc=libc-alpha@sourceware.org \
    --cc=llvm-dev@lists.llvm.org \
    --cc=tstellar@redhat.com \
    --cc=x86-64-abi@googlegroups.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).