From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Go in ptxdist
Date: Wed, 5 Oct 2016 18:31:17 +0200 [thread overview]
Message-ID: <20161005163117.mj7ctzvlqv35x762@pengutronix.de> (raw)
In-Reply-To: <20161005155510.GA1586@archie.localdomain>
Hi,
On Wed, Oct 05, 2016 at 05:55:10PM +0200, Clemens Gruber wrote:
> On Wed, Oct 05, 2016 at 03:13:27PM +0200, Michael Olbrich wrote:
> > I'd prefer it if we cleaned up the arm architecture stuff in
> > architecture.in to make this explicit.
>
> Do you mean adding config options for V5 and V7?
> And then deducing the correct GOARCH and GOARM from the ptxconfig
> settings instead of the used toolchain's ABI?
We should probably have options for v5/v6/v7 and for armel vs. armhf. And
checks, that the toolchain does the right thing. And then use these options
to configure Go correctly.
Side note: the toolchain check is non-trivial because there are gcc
versions that produce armhf code but do not define any macros that we could
use to identify this. I need to think about how to check this correctly.
This would be also interesting for other use-cases: I've worked with binary
software (OpenGL drives etc.) that couldn't compile. In that case, this
would be great to make sure things are consistent.
Mixing armel and armhf library does _not_ fail when starting the
application, but breaks later because the function argument are not
interpreted correctly...
> > > Go supports >=ARMv6 builds with hardfloat only, so I'd fall back to
> > > building ARMv5 binaries for ARMv6/7 softfloat configurations.
> >
> > Are you sure this means it cannot create armv6/7 softfloat?
>
> They write: "ARM on Linux. You must run an EABI kernel. These are
> generally known as armel for softfloat (compatible with ARMv5) or armhf
> for hardware floating point (ARMv6 and above)."
>
> If you set GOARM to 6 or 7 it always creates hardfloat code. So I think,
> setting it to anything else than 5 would lead to a crash on all
> architectures without a VFP unit?
This description is a bit vague. In general, whether armel or armhf is used
does not depend on the ARM architecture, so armel on ARMv7 (and using
floating point instructions!) is perfectly valid.
We need to investigate if armhf is just the default for ARMv6/7 or if that
can be configured.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-10-05 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 15:23 Clemens Gruber
2016-10-05 13:13 ` Michael Olbrich
2016-10-05 15:55 ` Clemens Gruber
2016-10-05 16:31 ` Michael Olbrich [this message]
2016-10-05 20:42 ` Clemens Gruber
2016-10-06 9:17 ` Michael Olbrich
2016-10-07 16:47 ` Clemens Gruber
2016-10-07 18:37 ` Uwe Kleine-König
2016-10-11 16:18 ` Clemens Gruber
2016-10-12 0:07 ` Clemens Gruber
2016-10-06 6:33 ` Uwe Kleine-König
2016-10-06 10:04 ` Marc Kleine-Budde
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=20161005163117.mj7ctzvlqv35x762@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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