public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/31676] Configuring with CC="gcc -march=x86-64-v3" --with-rtld-early-cflags=-march=x86-64 results in linker failure
Date: Wed, 24 Apr 2024 11:51:43 +0000	[thread overview]
Message-ID: <bug-31676-131-dtVA1zSCT6@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31676-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31676

--- Comment #5 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=46c999741340ea559784c20a45077955b50aca43

commit 46c999741340ea559784c20a45077955b50aca43
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Tue Apr 23 13:59:50 2024 -0700

    x86: Define MINIMUM_X86_ISA_LEVEL in config.h [BZ #31676]

    Define MINIMUM_X86_ISA_LEVEL at configure time to avoid

    /usr/bin/ld: â¦/build/elf/librtld.os: in function `init_cpu_features':
    â¦/git/elf/../sysdeps/x86/cpu-features.c:1202: undefined reference to
`_dl_runtime_resolve_fxsave'
    /usr/bin/ld: â¦/build/elf/librtld.os: relocation R_X86_64_PC32 against
undefined hidden symbol `_dl_runtime_resolve_fxsave' can not be used when
making a shared object
    /usr/bin/ld: final link failed: bad value
    collect2: error: ld returned 1 exit status

    when glibc is built with -march=x86-64-v3 and configured with
    --with-rtld-early-cflags=-march=x86-64, which is used to allow ld.so to
    print an error message on unsupported CPUs:

    Fatal glibc error: CPU does not support x86-64-v3

    This fixes BZ #31676.
    Reviewed-by: Sunil K Pandey <skpgkp2@gmail.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2024-04-24 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 19:12 [Bug dynamic-link/31676] New: " fweimer at redhat dot com
2024-04-23 19:13 ` [Bug dynamic-link/31676] " fweimer at redhat dot com
2024-04-23 19:23 ` hjl.tools at gmail dot com
2024-04-23 19:31 ` hjl.tools at gmail dot com
2024-04-23 19:40 ` fweimer at redhat dot com
2024-04-23 20:17 ` hjl.tools at gmail dot com
2024-04-23 20:45 ` skpgkp1 at gmail dot com
2024-04-24 11:51 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-25 11:18 ` cvs-commit at gcc dot gnu.org

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-31676-131-dtVA1zSCT6@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: 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).