public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmatti at linux dot vnet.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 17:29:18 +0000 [thread overview] Message-ID: <bug-31629-131-HPRN5uS4tQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31629-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31629 --- Comment #2 from Manjunath S Matti <mmatti at linux dot vnet.ibm.com> --- If glibc is configured without 'CFLAGS=-O2 -mcpu=power9', i.e. $ ./configure --prefix=/usr --with-headers=/usr/include --build=ppc64le-linux --with-cpu=power10 $ make This successfully builds glibc. Comparing the pass case with the fail case of acct.os we get 5c: 08 00 00 48 b 64 <__GI_acct+0x64> 60: 20 00 e3 4c bnslr+ 64: 00 00 00 48 b 64 <__GI_acct+0x64> - 64: R_PPC64_REL24_NOTOC __syscall_error + 64: R_PPC64_REL24 __syscall_error ... 70: 40 20 0c 00 .long 0xc2040 74: 68 00 00 00 .long 0x68 The build goes through because R_PPC64_REL24_NOTOC is generated. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-10 17:29 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 [this message] 2024-04-10 18:48 ` bergner at linux dot ibm.com 2024-04-10 20:45 ` bergner at linux dot ibm.com 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-HPRN5uS4tQ@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).