Github messages for voidlinux
 help / color / mirror / Atom feed
From: ejolson2005 <ejolson2005@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] All versions of 32-ARM Go compliers use software floating point.
Date: Thu, 13 May 2021 06:49:24 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30827@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

New issue by ejolson2005 on void-packages repository

https://github.com/void-linux/void-packages/issues/30827

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
Void 32-bit ARMv6 and ARMv7 versions of the Go compiler.  
### Expected behavior
The Go compiler will use hardware float by default for 32-bit ARMv7 platform and maybe even the ARMv6 platform.
### Actual behavior
The Go compiler packages are built without specifying GOARM=7 or GOARM=6 and apparently default to ARMv5 compatibility.
### Steps to reproduce the behavior
Compile any program that uses floating point and check performance.
### Possible fix
The Alpine Linux build scripts case things as
```
armel)  export GOARCH="arm" GOARM=5 ;;
armhf)  export GOARCH="arm" GOARM=6 ;;
armv7)  export GOARCH="arm" GOARM=7 ;;
```
which seems like a good idea to avoid everything defaulting to GOARM=5.


             reply	other threads:[~2021-05-13  4:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-13  4:49 ejolson2005 [this message]
2021-05-13  5:14 ` All versions of 32-bit ARM " ejolson2005
2021-05-13  6:08 ` ericonr
2021-05-14 17:29 ` ericonr
2022-05-19  2:16 ` github-actions
2022-05-19 14:52 ` [ISSUE] [CLOSED] " ericonr

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30827@inbox.vuxu.org \
    --to=ejolson2005@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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: link
Be 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 NNTP newsgroup(s).