Age | Commit message (Collapse) | Author | Files | Lines |
|
If mk gets into a bad state, it's not obvious that you can
remove the binary to force the rebuild. Also, not rebuilding
means that bugs in mkmk.sh are not noticed.
Just rebuild from scratch every time. It doesn't take too long
compared to the rest of INSTALL.
|
|
Also, if CC9FLAGS includes -fsanitize=address (ASAN),
predefine PLAN9PORT_ASAN for use by programs that need
to know (mainly libthread).
The 9c script used to have a variable called ngflags, which
was ccflags except -g (ng stood for "no g"), but nothing needs
it split out anymore, so simplify to just ccflags.
|
|
Found by ASAN.
|
|
getdirentries(2) has been deprecated on macOS since 10.5 (ten releases ago).
Using it requires disabling 64-bit inodes, but that in turn makes binaries
incompatible with some dynamic libraries, most notably ASAN.
At some point getdirentries(2) will actually be removed.
For both these reasons, switch to opendir/readdir.
A little clunky since we have to keep the DIR* hidden away
to preserve the int fd interfaces, but it lets us remove a bunch
of OS-specific code too.
|
|
More preparation for opendir.
|
|
More preparation for opendir.
|
|
Preparation for using opendir.
|
|
atomics were added in GCC 4.9: https://gcc.gnu.org/gcc-4.9/changes.html
|
|
|
|
|
|
|
|
C11 is apparently too new for these systems.
Fixes #55.
|
|
|
|
|
|
|
|
dd fans rejoice!
Also helps with commands like go test -run=x.
|
|
This fixes at least one shell script (printfont) that expected
'x'`{y}'z'
to mean
'x'^`{y}^'z'
as it now does. Before it meant:
'x'^`{y} 'z'
One surprise is that adjacent lists get a free carat:
(x y z)(1 2 3)
is
(x1 y2 z3)
This doesn't affect any rc script in Plan 9 or plan9port.
|
|
|
|
The old yacc-based parser is available with the -Y flag,
which will probably be removed at some point.
The new -D flag dumps a parse tree of the input,
without executing it. This allows comparing the output
of rc -D and rc -DY on different scripts to see that the
two parsers behave the same.
The rc paper ends by saying:
It is remarkable that in the four most recent editions of the UNIX
system programmer’s manual the Bourne shell grammar described in the
manual page does not admit the command who|wc. This is surely an
oversight, but it suggests something darker: nobody really knows what
the Bourne shell’s grammar is. Even examination of the source code is
little help. The parser is implemented by recursive descent, but the
routines corresponding to the syntactic categories all have a flag
argument that subtly changes their operation depending on the context.
Rc’s parser is implemented using yacc, so I can say precisely what the
grammar is.
The new recursive descent parser here has no such flags.
It is a straightforward translation of the yacc.
The new parser will make it easier to handle free carats
in more generality as well as potentially allow the use of
unquoted = as a word character.
Going through this exercise has highlighted a few
dark corners here as well. For example, I was surprised to
find that
x >f | y
>f x | y
are different commands (the latter redirects y's output).
It is similarly surprising that
a=b x | y
sets a during the execution of y.
It is also a bit counter-intuitive
x | y | z
x | if(c) y | z
are not both 3-phase pipelines.
These are certainly not things we should change, but they
are not entirely obvious from the man page description,
undercutting the quoted claim a bit.
On the other hand, who | wc is clearly accepted by the grammar
in the manual page, and the new parser still handles that test case.
|
|
Version 10 of gcc enforces -fno-common which breaks a lot of things.
This fix reverts to the pre-10 behaviour. The real fix is to clean up
stray redefinitions which should be declarations.
|
|
This avoids reopening collapsed windows after a large vertical resize.
|
|
Fixes #357
|
|
Fixes #363
Change-Id: Ic8ad5ccce3935fdf00732d78d3024b535db90447
|
|
and not unexpectedly quitting an application.
Fixes #360
|
|
|
|
Missed in 0b349f6f that Bterm is not closing fd.
|
|
|
|
|
|
OpenBSD is using pthreads now, so no need for tas.
|
|
Also reduce duplication: makecontext is per-arch not per-os-arch.
May fix #353.
|
|
It may be that pthreads on NetBSD is now good enough,
but the build as written (introduced in 23a2368 at my suggestion)
is certainly broken, since both NetBSD.c and pthread.c define
the same functions.
If NetBSD does support pthreads now, then a few things
should happen together:
- libthread/sysofiles.sh should drop its top NetBSD case entirely
- libthread/NetBSD.c should be deleted
- libthread/NetBSD-*-asm.s should be deleted
- include/u.h's NetBSD case should define PLAN9PORT_USING_PTHREADS
and #include <pthread.h>
For now, restore to less clearly broken build.
|
|
Linux 2.4 is dead.
(The libthread code hasn't worked for Linux 2.4 for a long time.)
|
|
Linux.c was for Linux 2.4 and is no longer used directly,
only indirectly because NetBSD.c was a 1-line file #including Linux.c.
So mv Linux.c NetBSD.c.
Also rm Linux-*-asm.s which was for Linux 2.4 as well.
|
|
More dead code.
|
|
Darwin 11.0.0 was Mac OS X 10.7.0 aka Lion.
The previous version was Snow Leopard, which
has been unsupported by Apple since February 2014.
|
|
Pretty sure FreeBSD 4 is gone now. :-)
|
|
This should have been deleted in 20f5692b (2012-07-14),
which removed the mkfile and sysofiles.sh references to it.
|
|
They were just a duplicate of my(get|set)mcontext from the other
assembly file, and unused from threadimpl.h.
Change-Id: Id8003e5177ed9d37a7f0210037acbe55bbf7f708
|
|
Fixes #195.
Signed-off-by: Dan Cross <cross@gajendra.net>
|
|
Fixes #3.
|
|
Signed-off-by: Dan Cross <cross@gajendra.net>
|
|
The issue manifests in fork: POSIX fork mandates that a
fork'd process is created with a single thread. If a
multithreaded program forks, and some thread was in
malloc() when the fork() happened, then in the child
the lock will be held but there will be no thread to
release it.
We assume the system malloc() must already know how to
deal with this and is thread-safe, but it won't know about
our custom spinlock. Judging that this is no longer
necessary (the lock code was added 15 years ago) we remove
it.
Signed-off-by: Dan Cross <cross@gajendra.net>
|
|
POSIX setenv does everything that p9putenv's body,
so just delegate to that.
Signed-off-by: Dan Cross <cross@gajendra.net>
|
|
Fixes #347.
|
|
|
|
The ptrace handlers wanted to take u64int arguments,
not ulong.
Signed-off-by: Dan Cross <cross@gajendra.net>
|
|
Fixes #54.
|
|
Fixes #340.
Fixes #343.
|
|
Unclear whether the old semantics were the right ones,
but at least this preserves what they've been for the past
however many years.
|
|
|