Hi Amit,
I'm surprised to see that OpenBSD uses only 1024 for BUFSIZ, and - even
more - that PIPE_BUF is only 512 (all others so far use 4096 or 5120).
Especially the size of PIPE_BUF is critical for performance, as this is
the limit for atomic messages over pipes, used heavily in PicoLisp's
On Thu, Aug 25, 2011 at 12:42:02PM +0200, Alexander Burger wrote:
Now I created a first x86-64.openBsd.defs.l (see attachment).
Oops, forgot some lines. I've now changed here:
71c71
(equ TERMIOS (+ 60 4)) # Terminal I/O structure (+ Padding)
---
(equ TERMIOS (+ 44 4)) # Terminal
Hi,
Background: I am trying to port picoLisp with Alex's help, its written
in assembly for 64 bit architectures and C for 32 bit arches. He is
ported to amd64, ppc64 and sparc64 is on his roadmap.
Can somebody please weigh in on Alex's comment?
thanks
-- Forwarded message --
Hi Randall,
However: Questions back to Alex: How large are the atomic messages
over pipes in picolisp, on average? I think you don't actually send the
data over the pipe, but just block addresses in a DB have been updated. I
am curious about this myself.
Yes, correct. Only external symbols
I set most values as they are in your output. However, there are also
some values not covered by def.c, because I took them directly from the
include files. These concern the ranges
ENOENT .. ECONNRESET
O_RDONLY .. O_APPEND
SIGHUP .. SIGNALS
TM_SEC .. TM_YEAR
Could you
