From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0CF1B3858C2C; Fri, 11 Feb 2022 03:54:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CF1B3858C2C From: "archicharmer at mail dot ru" To: glibc-bugs@sourceware.org Subject: [Bug ports/28872] Building glibc for MIPSel single float targets Date: Fri, 11 Feb 2022 03:54:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: ports X-Bugzilla-Version: 2.30 X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: archicharmer at mail dot ru X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: INVALID 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: Fri, 11 Feb 2022 03:54:47 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D28872 --- Comment #12 from Den --- (In reply to Adhemerval Zanella from comment #11) > I am not really proposing it, I am in fact trying to understand what gcc > emits in such case. For instance, > [...] >=20 > So I am trying to understand how/when gcc does the double emulation that > replaces > s.d by a two sdc1. I'll write the part of the additions to configures for how binutils and gcc were built. binutils-2.34 . --target=3Dmipsel-unknown-linux-gnu --with-arch=3Dr6000 --with-cpu=3Dr6000 gcc-9.2.0 . --target=3Dmipsel-unknown-linux-gnu --with-arch=3Dr6000 --with-float=3Dhard --with-fpu=3Dsingle It is not actually gcc emulates s.d as a two sdc1 (swc1 attentionly) (gcc o= nly "rumbles" when it meets an unsupported opcode in asm volatile), I got that conception from this: echo 's.d $f0,($0)' >test.s mipsel-unknown-linux-gnu-as test.s mipsel-unknown-linux-gnu-objdump -d a.out 00000000 <.text>: 0: e4000000 swc1 $f0,0(zero) 4: e4010004 swc1 $f1,4(zero) > Is the segfault due the patch or is it another issue in fact? Well, I could not determine that exactly because I can not build it without= the patch. If to build a compiler without fp then everything is working fine and there is no such SegFaults in those places. Actually, no one existing libc can not be built for MIPSel target when there are the single floats only, because there are the same files with same includings to compile. Same structure of files for FPU. > Patch is not acceptable *as-is* I mean the patch itself, the conception in it, is doing wrong. > I think it still possible to fix the > context functions to correctly work on the chip you are using. Well, that is already behind my abilities. The patch was everything I got. --=20 You are receiving this mail because: You are on the CC list for the bug.=