public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "archicharmer at mail dot ru" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug ports/28872] Building glibc for MIPSel single float targets Date: Thu, 10 Feb 2022 19:45:39 +0000 [thread overview] Message-ID: <bug-28872-131-DrJMGUVSOu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28872-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28872 Den <archicharmer at mail dot ru> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #10 from Den <archicharmer at mail dot ru> --- (In reply to Adhemerval Zanella from comment #9) > I am trying to understand which options you use with gcc to target this > chip, > -mabi=32 -march=mips2 -mhard-float -msingle-float -mfp32 That's correct. -march=r6000 but yes it is mips2 anyway. > seems to use > 'sw/lw' to > load store doubles. I do not think that if to replace all of the s.d/l.d to sw/lw respectively will do the trick. Let's summarize. There is no way to somehow split a doubleword to a two words and vice versa conversion/uniting; An extra ABI is required to be specified as to be thought-out. No one will be handling that because of it's rarity; even if the processor itself, it's model, is not rare; Most of the programs compiled basely on glibc with my patch are providing a SegFault, invalid write access. Patch is a waste, it's conception is wrong. Verdicts are: patch is not worth to be accepated, even to be existing; glibc can not be built for MIPSel targets with single float only; thread closed; invalid (to be as a) bug request. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-10 19:45 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-08 11:27 [Bug ports/28872] New: " archicharmer at mail dot ru 2022-02-08 17:55 ` [Bug ports/28872] " joseph at codesourcery dot com 2022-02-08 19:19 ` archicharmer at mail dot ru 2022-02-08 19:34 ` joseph at codesourcery dot com 2022-02-09 3:41 ` archicharmer at mail dot ru 2022-02-09 14:16 ` adhemerval.zanella at linaro dot org 2022-02-09 17:03 ` archicharmer at mail dot ru 2022-02-09 17:33 ` adhemerval.zanella at linaro dot org 2022-02-10 2:43 ` archicharmer at mail dot ru 2022-02-10 11:25 ` adhemerval.zanella at linaro dot org 2022-02-10 19:45 ` archicharmer at mail dot ru [this message] 2022-02-10 20:57 ` adhemerval.zanella at linaro dot org 2022-02-11 3:54 ` archicharmer at mail dot ru 2022-02-17 17:09 ` archicharmer at mail dot ru 2022-02-18 12:39 ` adhemerval.zanella at linaro dot org 2022-02-19 8:27 ` archicharmer at mail dot ru 2022-02-22 20:05 ` adhemerval.zanella at linaro dot org 2022-02-23 8:06 ` archicharmer at mail dot ru 2022-02-23 11:57 ` adhemerval.zanella at linaro dot org 2022-02-23 11:57 ` adhemerval.zanella at linaro dot org 2022-03-05 17:43 ` archicharmer at mail dot ru 2022-03-07 11:07 ` adhemerval.zanella at linaro dot org 2022-03-07 16:17 ` archicharmer at mail dot ru 2022-03-07 16:59 ` adhemerval.zanella at linaro dot org 2022-03-18 15:01 ` archicharmer at mail dot ru
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-28872-131-DrJMGUVSOu@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).