9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: kokamoto@hera.eonet.ne.jp, 9front@9front.org
Subject: Re: [9front] adding javascript enable to netsurf
Date: Thu, 12 Mar 2020 21:58:41 -0700	[thread overview]
Message-ID: <416ACE4C189DEB5FEDC699884BBB0588@eigenstate.org> (raw)
In-Reply-To: <640113AC11648AFD73090E4C6B1219B9@hera.eonet.ne.jp>

>> However, I'm now running it on 1GB rpi3, it corrupted.
>> I'll compile netsurf on a 386 machine tommorrow.
> 
> I did it.
> term% ls -l 8.nsfb
> --rwxr-xr-x M 26 kokamoto kokamoto 46841407 Mar 13 11:20 8.nsfb
> 
> It's worse...
> 
> I got:
> term% ./8.nsfb
> INITING display!
> 8.nsfb 51407: suicide: sys: fp: invalid operation fppc=0xf8dc6 status=0xb8a3 pc=0x000e5026
> 
> I'll take a rest, and investigate what's going on here.
> 
> Kenji

Plan 9 is stricter about floating point operations like division by zero. It can
be made to behave more like Unix by calling setfcr at the start of the program.
I think something like:

	setfcr(getfcr() & ~(FPINVAL|FPZDIV|FPOVFL));

will do the job.



  reply	other threads:[~2020-03-13  4:58 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  4:33 kokamoto
2020-03-13  4:58 ` ori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-14  5:04 kokamoto
2020-04-14 21:53 ` Kyle Nusbaum
2020-04-15 20:05   ` jamos
2020-04-15 20:24     ` ori
2020-04-18  1:09       ` Kyle Nusbaum
2020-04-18  1:19         ` ori
2020-04-18 17:11           ` Eli Cohen
2020-04-18 17:15             ` telephil9
2020-04-18 17:17             ` ori
2020-04-13 23:46 kokamoto
2020-04-07  4:25 kokamoto
2020-04-06  5:48 kokamoto
2020-04-13 12:44 ` jamos
2020-04-05  4:52 kokamoto
2020-04-05  4:41 kokamoto
2020-03-22 23:47 kokamoto
2020-03-22  2:19 kokamoto
2020-03-21  3:24 kokamoto
2020-03-22 20:27 ` jamos
2020-03-22 20:54   ` ori
2020-03-22 20:54   ` ori
2020-03-20  5:49 kokamoto
2020-03-20 16:10 ` Kyle Nusbaum
2020-03-20 16:15   ` ori
2020-03-20 17:12     ` telephil9
2020-03-20 17:40       ` Jens Staal
2020-03-20 18:54     ` jamos
2020-03-21  5:00       ` Jens Staal
2020-03-21 12:24         ` Ethan Gardener
2020-03-20 22:07     ` Kyle Nusbaum
2020-03-17 11:16 kokamoto
2020-03-17 17:42 ` jamos
2020-03-15  9:42 kokamoto
2020-03-15 11:06 ` Steve Simon
2020-03-15 11:38   ` Jens Staal
2020-03-15 13:50   ` jamos
2020-03-14  1:49 kokamoto
2020-03-14  2:09 ` ori
2020-03-14  1:19 kokamoto
2020-03-14  1:34 ` ori
2020-03-12  5:28 kokamoto
2020-03-12  2:20 kokamoto
2020-03-12  2:43 ` ori
2020-03-11 23:59 kokamoto
2020-03-11 10:27 kokamoto
2020-03-11  6:36 kokamoto
2020-03-11  9:29 ` [9front] " jamos

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=416ACE4C189DEB5FEDC699884BBB0588@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).