On Thursday 21 November 2013 22:37:06 Fausto Saporito wrote:
> Hi Jens,
>
> thanks a lot!!! that site is wonderful :-D
>
> regards,
> Fausto
>
>
Thanks :)
If you want more language support (and more up-to-date fortran, but also ObjC,
COBOL, C++ ...) it is highly recommended to check out the
On Fri, Nov 22, 2013 at 1:02 AM, Jeff Sickel wrote:
> Will one of you describe the flicker you speak of? I see flicker on
> Linux’s drawterm X11 when resizing rio windows and other operations,
> given the round trip time, though the flicker is less on fast local
> networks.
You are right, of co
Well, I wrote `the current sources', but that was wrong: I just
checked bitbucket again and saw your commits of the last few hours. So
I pulled the updates and rebuilt. To my surprise, the phenomena remain
exactly the same. This time I got a message though:
objc[3785]: Object 0x7fb261297930 of cla
Hi Jens,
Thanks for the infos. I prefer to use just pcc and 8c, but I understand the
changes to make to some progs are many in order to compile with pcc.
By the way I have always the same problem (suicide with stack overflow
running arithchk).
I'm thinking this could be related to virtualbox... m
In Plan 9 acme, if you type
{}
then go back and type text between the brackets
{Curiouser and curiouser!}
the right arrow is blocked when you want to go over the closing
bracket to continue typing to its right. (If you first go to the left,
and then back to the right, it works.)
Same for the o
On Fri Nov 22 08:22:29 EST 2013, vanattenm...@gmail.com wrote:
> In Plan 9 acme, if you type
>
> {}
>
> then go back and type text between the brackets
>
> {Curiouser and curiouser!}
>
> the right arrow is blocked when you want to go over the closing
> bracket to continue typing to its right. (
> By the way I have always the same problem (suicide with stack overflow
> running arithchk).
that's not a stack overflow, that's a x87 floating point stack overflow.
if you would post the code around the program counter in your error
message it would be helpful. asm(*PC) with acid would be even
That is very quick---thanks, Erik! I just tried out the patch on Bell
Labs Plan 9, and it works fine.
Mark.
Hi Erik,
yes, it's a FP stack overflow... :-)
I also tried with 9front, and the error message is slightly different:
./arithchk
#define IEEE_8087
#define Arith_Kind_ASL 1
arithchk 8523: suicide: sys: fp: invalid operation fppc=0x12ee
status=0xb8b3 pc=0x12f2
further checks reveal that the pro
you might want to disable that exception in main()
setfcr(getcfr() ~FPOVFL);
sometimes I had to go extreme and do:
setfcr(getfcr() &~ (FPINEX|FPOVFL|FPUNFL|FPZDIV|FPINVAL));
when porting some code that was supposed to run well on unixes.
see getfcr(2).
On Nov 22, 2013, at 2:42 PM, Fausto Sapori
just applied to 9front. thank you mark and erik. :-)
--
cinap
> get_nanbits(unsigned int *b, int k)
> {
> union { double d; unsigned int z[2]; } u, u1, u2;
>
> k = 2 - k;
> u1.z[k] = u2.z[k] = 0x7ff0;
> u1.z[1-k] = u2.z[1-k] = 0;
> u.d = u1.d - u2.d; /* Infinity - Infinity */ <<<== this is the
> FATAL ERROR.
> b[0] = u.z[0];
> b[1] = u.z[1];
>
Hi Erik and Federico,
thanks a lot!
regards,
Fausto
On 22 November 2013 16:42, Fausto Saporito wrote:
> yes, it's a FP stack overflow... :-)
often that means that there is a function that should be declared to return
a float or double
but is relying on a default declaration as int, or is declared, but
incorrectly.
14 matches
Mail list logo