From: kokamoto@hera.eonet.ne.jp
To: 9front@9front.org
Subject: Re: [9front] 5l problem on python276 compilation
Date: Tue, 14 Jul 2020 13:58:00 +0900 [thread overview]
Message-ID: <59602E12A39AA3358F71EFE1258A33B3@hera.eonet.ne.jp> (raw)
In-Reply-To: <73F56EAAD59BD2083DB0F3DE602AF828@eigenstate.org>
> 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?
I did, and the result is the same:
mkconfig config-$objtype >config-$objtype.c
pcc -TVwc -I.. -I../Include -DTarm -DPLAN9APE -DPy_BUILD_CORE -DNDEBUG LDFLAGS=-F config-arm.c
pcc -o 5.out config-arm.5 python.5 libpython.a5 libz.a5 libbz2.a5 /arm/lib/ape/libmp.a /arm/lib/ape/libsec.a /arm/lib/ape/lib9.a
@{
cd ..
Plan9/5.out -E -S -m sysconfig --generate-posix-vars
}
5.out 6759: warning: emulated arm7500 fpa instr 0xee500110 at 0x22ae90
5.out 6759: suicide: illegal instruction: VFP opcode in emulated mode
mk: @{ cd ... : exit status=rc 6756: rc 6758: 5.out 6759: illegal instruction: VFP opcode in emulated mode, deleting '../pybuilddir.txt'
mk: @{ cd ... : exit status=rc 481: rc 483: mk 6668: error
mk 476: error
Kenji
next prev parent reply other threads:[~2020-07-14 4:58 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
2020-07-14 4:58 ` kokamoto [this message]
-- 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=59602E12A39AA3358F71EFE1258A33B3@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9front@9front.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).