From: ori@eigenstate.org
To: kokamoto@hera.eonet.ne.jp, 9front@9front.org
Subject: Re: [9front] 5l problem on python276 compilation
Date: Sun, 12 Jul 2020 20:20:27 -0700 [thread overview]
Message-ID: <73F56EAAD59BD2083DB0F3DE602AF828@eigenstate.org> (raw)
In-Reply-To: <6A3433BEF26855565899E619E03A4CA7@hera.eonet.ne.jp>
>> /* Define if C doubles are 64-bit IEEE 754 binary format, stored in ARM
>> mixed-endian order (byte order 45670123) */
>> #define DOUBLE_IS_ARM_MIXED_ENDIAN_IEEE754 1
>
> In addition, I can build python276 for 386, amd64 and arm64, but
> only arm fails by the reason mentioned before.
>
> Please remind the case of netsurf, it works fine for 386, amd64 and arm64,
> but don't work as expected for arm. I suppoose this by the same reason...
>
> Kenji
So, I'll try to figure out how to get an arm cpu server soon to test,
but:
5.out 7040: warning: emulated arm7500 fpa instr 0xee500110 at 0x22ae90
5.out 7040: suicide: illegal instruction: VFP opcode in emulated mode
mk: @{ cd ... : exit status=rc 7037: rc 7039: 5.out 7040: illegal instruction: VFP opcode in emulated mode, deletin
It sounds like we're somehow generating mixed VFP and arm7500 floating
point instructions, but we should only be generating one of them. I think
we should be defaulting to VFP.
For the sake of testing, can you try adding LDFLAGS=-F when building
for arm?
next prev parent reply other threads:[~2020-07-13 3:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 0:22 kokamoto
2020-07-12 5:29 ` kokamoto
2020-07-12 5:38 ` ori
2020-07-12 23:30 ` kokamoto
2020-07-13 2:42 ` kokamoto
2020-07-13 3:20 ` ori [this message]
2020-07-14 4:58 ` kokamoto
-- strict thread matches above, loose matches on Subject: below --
2020-07-11 22:10 kokamoto
2020-07-11 22:28 ` [9front] " kokamoto
2020-07-12 0:22 ` kokamoto
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=73F56EAAD59BD2083DB0F3DE602AF828@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=kokamoto@hera.eonet.ne.jp \
/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).