public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "akhilesh.k at samsung dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/31488] New: undefined reference to `fmod'" error for i586 Date: Thu, 14 Mar 2024 14:01:53 +0000 [thread overview] Message-ID: <bug-31488-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31488 Bug ID: 31488 Summary: undefined reference to `fmod'" error for i586 Product: glibc Version: 2.38 Status: NEW Severity: normal Priority: P2 Component: math Assignee: unassigned at sourceware dot org Reporter: akhilesh.k at samsung dot com Target Milestone: --- Hi I am using glibc 2.38, while Some of external module compilation I observed "undefined reference to `fmod'" error. I observed this only in x586 for risc-v working fine. Reason, for i586 no "fmod" week symbol in libm.so, but same symbol is available in risc-v compiled libm.so Looks this behaviour is due to below changes. https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=16439f419b270184ec501c531bf20d83b6745fb0 i586 (no fmod week symbol) khilesh.k@DELL-BUILD01:~source/build$ nm lib/libm.so.6 | grep fmod 00000000000252a0 t __fmod 0000000000010af0 t __fmod_compat 00000000000143f0 t __fmod_compatf 0000000000038010 t __fmodf 0000000000063fb0 t __fmodf128 0000000000063fb0 W fmodf128 00000000000476e0 T __fmodf128_finite@GLIBC_2.26 0000000000038010 W fmodf32 00000000000252a0 W fmodf32x 00000000000252a0 W fmodf64 000000000000f320 W fmodf64x 0000000000038010 T __fmodf_finite@GLIBC_2.15 00000000000143f0 T fmodf@GLIBC_2.2.5 0000000000038010 T fmodf@@GLIBC_2.38 00000000000252a0 T __fmod_finite@GLIBC_2.15 0000000000010af0 T fmod@GLIBC_2.2.5 00000000000252a0 T fmod@@GLIBC_2.38 000000000000f320 t __fmodl 000000000000f320 W fmodl 0000000000015950 T __fmodl_finite@GLIBC_2.15 00000000000252a0 t __ieee754_fmod 0000000000038010 t __ieee754_fmodf 00000000000476e0 t __ieee754_fmodf128 0000000000015950 t __ieee754_fmodl 00000000000252a0 t __SI__fmod_1 0000000000010af0 t __SI__fmod_compat_0 00000000000143f0 t __SI__fmod_compatf_0 0000000000038010 t __SI__fmodf_0 00000000000252a0 t __SI__ieee754_fmod_0 0000000000038010 t __SI__ieee754_fmodf_1 00000000000476e0 t __SI__ieee754_fmodf128_0 0000000000015950 t __SI__ieee754_fmodl_0 Risc-v result (W fmod) khilesh.k@DELL-BUILD01:~$ nm ./riscv64-none-linux-gnu/sys-root/lib64/lp64d/libm.so.6 | grep fmod 0000000000026c12 t __fmod 0000000000026c12 W fmod 00000000000346f2 t __fmodf 00000000000346f2 W fmodf 00000000000237e0 W fmodf128 00000000000346f2 W fmodf32 0000000000026c12 W fmodf32x 0000000000026c12 W fmodf64 00000000000237e0 W fmodf64x Thanks Akhilesh -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-14 14:01 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-14 14:01 akhilesh.k at samsung dot com [this message] 2024-03-14 14:06 ` [Bug math/31488] " akhilesh.k at samsung dot com 2024-03-14 14:07 ` [Bug math/31488] undefined reference to `fmod'" error on i586 akhilesh.k at samsung dot com 2024-03-14 15:59 ` adhemerval.zanella at linaro dot org 2024-03-14 16:08 ` schwab@linux-m68k.org 2024-03-14 16:14 ` schwab@linux-m68k.org 2024-03-14 16:16 ` adhemerval.zanella at linaro dot org 2024-03-14 22:38 ` sam at gentoo dot org 2024-05-10 9:41 ` akhilesh.k at samsung dot com 2024-05-10 16:19 ` adhemerval.zanella at linaro dot 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-31488-131@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).