public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at linux dot ibm.com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/31629] powerpc64: Configuring with "--with-cpu=power10" and 'CFLAGS=-O2 -mcpu=power9' fails to build glibc Date: Wed, 10 Apr 2024 20:45:00 +0000 [thread overview] Message-ID: <bug-31629-131-NnqFW7uuNi@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31629-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31629 Peter Bergner <bergner at linux dot ibm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amodra at gmail dot com, | |fweimer at redhat dot com, | |tuliom at ascii dot art.br --- Comment #3 from Peter Bergner <bergner at linux dot ibm.com> --- The above code comes from sysdeps/powerpc/powerpc64/sysdep.h: b JUMPTARGET (NOTOC (__syscall_error)) The NOTOC macro defined in the same file is defined as: #ifdef USE_PPC64_NOTOC # define NOTOC(l) l@notoc #else # define NOTOC(l) l #endif ...and USE_PPC64_NOTOC is a configure time macro from sysdeps/powerpc/powerpc64/configure.ac: AC_CACHE_CHECK([if the compiler supports @notoc], libc_cv_ppc64_notoc, [dnl cat > conftest.c <<EOF int bar (void); int foo (void) { return bar () + 1; } EOF libc_cv_ppc64_notoc=no if AC_TRY_COMMAND([${CC-cc} $libc_cv_cc_submachine $CFLAGS $CPPFLAGS -S -o conftest.s conftest.c]) \ && AC_TRY_COMMAND([grep -q -E 'bar@notoc' conftest.s]) then libc_cv_ppc64_notoc=yes fi rm -rf conftest.*]) The "bug" is that $libc_cv_cc_submachine (ie, -mcpu=power10 from the --with-cpu=power10 configure option) is overridden by the -mcpu=power9 from the CLFAGS. The following GLIBC patch fixes the error for me: @@ -35,7 +35,7 @@ int bar (void); int foo (void) { return bar () + 1; } EOF libc_cv_ppc64_notoc=no - if AC_TRY_COMMAND([${CC-cc} $libc_cv_cc_submachine $CFLAGS $CPPFLAGS -S -o conftest.s conftest.c]) \ + if AC_TRY_COMMAND([${CC-cc} $CFLAGS $CPPFLAGS $libc_cv_cc_submachine -S -o conftest.s conftest.c]) \ && AC_TRY_COMMAND([grep -q -E 'bar@notoc' conftest.s]) then libc_cv_ppc64_notoc=yes -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-10 20:45 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-10 17:10 [Bug build/31629] New: " mmatti at linux dot vnet.ibm.com 2024-04-10 17:14 ` [Bug build/31629] " mmatti at linux dot vnet.ibm.com 2024-04-10 17:16 ` mmatti at linux dot vnet.ibm.com 2024-04-10 17:21 ` mmatti at linux dot vnet.ibm.com 2024-04-10 17:29 ` mmatti at linux dot vnet.ibm.com 2024-04-10 18:48 ` bergner at linux dot ibm.com 2024-04-10 20:45 ` bergner at linux dot ibm.com [this message] 2024-04-10 20:54 ` bergner at linux dot ibm.com 2024-04-10 23:20 ` amodra at gmail dot com 2024-04-11 2:17 ` mmatti at linux dot vnet.ibm.com 2024-04-13 12:07 ` fweimer at redhat dot com 2024-04-13 12:12 ` fweimer at redhat dot com 2024-04-24 7:10 ` amodra at gmail dot com
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-31629-131-NnqFW7uuNi@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: linkBe 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).