public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug math/28481] Glibc "--disable-mathvec" configure option fail to disable traces to libmvec Date: Thu, 21 Oct 2021 16:25:45 +0000 [thread overview] Message-ID: <bug-28481-131-UyTiFZbiO1@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28481-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28481 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- A remark on what the ideal approach for fixing this should be: Installed headers don't normally depend on how glibc is configured, except for the chosen ABI, but in this case some such dependency is needed. It's also possible for a set of installed headers to be shared between multiple ABIs, each with glibc built separately, and bits/math-vector.h and finclude/math-vector-fortran.h duly contain conditionals to reflect that mathvec functionality is supported for x86_64 (both 64-bit and x32 ABIs) but not for i386. In principle, someone could build x86_64 glibc with libmvec and x32 glibc without and have them using the same installed headers. To me, this suggests having another generated installed header using the same logic as for gnu/lib-names.h and gnu/stubs.h: there is a wrapper header, which contains conditionals to include the appropriate ABI-specific header. And the ABI-specific header, say gnu/mathvec.h, would define e.g. __LIBMVEC_ENABLED to 0 or 1, and be included by bits/math-vector.h to provide an additional conditional for whether the functionality is available. Only the generated ABI-specific header would depend on how glibc was configured. However, I don't know if this would work for the Fortran case: whether such a structure with an ABI-specific header that might depend on how glibc was configured, and an ABI-independent header that doesn't, can be used in for Fortran. If it won't work for Fortran, maybe you need to fall back to the simpler but less general approach of using different sysdeps directories, and thus different versions of the installed finclude/math-vector-fortran.h, depending on whether --disable-mathvec is used (but still trying to get i386 glibc with default configure options to install a version suitable for use with x86_64 glibc with default configure options). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-10-21 16:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-21 6:39 [Bug math/28481] New: " haochen.jiang at intel dot com 2021-10-21 16:25 ` joseph at codesourcery dot com [this message] 2021-10-22 12:53 ` [Bug math/28481] " hjl.tools 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-28481-131-UyTiFZbiO1@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).