From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BDF903858416; Thu, 21 Oct 2021 16:25:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BDF903858416 From: "joseph at codesourcery dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: math X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2021 16:25:45 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28481 --- Comment #1 from 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= =20 for the chosen ABI, but in this case some such dependency is needed. It's= =20 also possible for a set of installed headers to be shared between multiple= =20 ABIs, each with glibc built separately, and bits/math-vector.h and=20 finclude/math-vector-fortran.h duly contain conditionals to reflect that=20 mathvec functionality is supported for x86_64 (both 64-bit and x32 ABIs)=20 but not for i386. In principle, someone could build x86_64 glibc with libmvec and x32 glibc=20 without and have them using the same installed headers. To me, this=20 suggests having another generated installed header using the same logic as= =20 for gnu/lib-names.h and gnu/stubs.h: there is a wrapper header, which=20 contains conditionals to include the appropriate ABI-specific header.=20=20 And the ABI-specific header, say gnu/mathvec.h, would define e.g.=20 __LIBMVEC_ENABLED to 0 or 1, and be included by bits/math-vector.h to=20 provide an additional conditional for whether the functionality is=20 available. Only the generated ABI-specific header would depend on how=20 glibc was configured. However, I don't know if this would work for the Fortran case: whether=20 such a structure with an ABI-specific header that might depend on how=20 glibc was configured, and an ABI-independent header that doesn't, can be=20 used in for Fortran. If it won't work for Fortran, maybe you need to fall= =20 back to the simpler but less general approach of using different sysdeps=20 directories, and thus different versions of the installed=20 finclude/math-vector-fortran.h, depending on whether --disable-mathvec is=20 used (but still trying to get i386 glibc with default configure options to= =20 install a version suitable for use with x86_64 glibc with default=20 configure options). --=20 You are receiving this mail because: You are on the CC list for the bug.=