From: Romano <unobe@cpan.org>
To: 9front@9front.org
Subject: Re: arm64 fails to link when float converted to int (Was Re: [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG))
Date: Sat, 1 Aug 2020 11:41:55 -0700 [thread overview]
Message-ID: <4805B3AEFECCAC9B0E43ACC47F838B40@smtp.pobox.com> (raw)
> this is clearly a compiler bug.
>
> lets compare with the other compilers:
> ...
Thank you very much for the guided walk-through, and providing a patch to fix! It's been two decades since I looked at assembler before this past week or so, and therefore your notes were helpful in giving me an overview of what was happening (the -S flag is handy). I still need to take some more time in order to really understand the architectural differences (e.g., the intel 'haha' moment), but some other projects are most likely going to take priority if I don't run into any other compiler bugs.
> we'll need to to do a bunch of test now to make sure this
> change doesnt break anything.
>
> feel free to test and report any errors would be appreciated.
On my rpi4, I re-made 7c with the patch and installed it, then did 'cd /sys/src; mk clean; mk': no error occurred. I also reverted the modification I had made for netsurf native, mk clean'd, and it built without modification too.
Should I be kicking the tires in some other way?
next reply other threads:[~2020-08-01 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 18:41 Romano [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-21 15:54 netsurf native frontend telephil9
2020-05-21 17:59 ` [9front] " Romano
2020-07-28 7:11 ` [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG) Romano
2020-07-29 6:08 ` arm64 fails to link when float converted to int (Was Re: [9front] netsurf native frontend (text_insert: illegal combination FCVTZSDW FCON NONE REG)) Romano
2020-08-01 11:43 ` cinap_lenrek
2020-08-01 12:23 ` Anthony Martin
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=4805B3AEFECCAC9B0E43ACC47F838B40@smtp.pobox.com \
--to=unobe@cpan.org \
--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).