| Age | Commit message (Collapse) | Author |
|---|
|
instead of .sp -1v, which for example Solaris nroff handles poorly.
Problem report and patch by millert@,
with the print_word chunk tweaked by me.
|
|
from /etc/rc(8). This prevents the warning to be displayed at shutdown
time when the script has rc_stop=NO.
req. and input from fgsch@
"go ahead" schwarze@
input from an ok halex@, ok robert@
|
|
ok halex@
|
|
Inspired by a diff from millert@, but implemented rather
differently and with slightly better functionality.
In particular, this one respects -offset and -width
arguments found in the input file.
|
|
everywhere instead of setting splbio.
ok krw@ pirofti@
|
|
On x86, the xchg operation between reg and mem has an implicit lock
prefix, i.e. on MP, it is a relatively expensive atomic operation.
This is not needed here.
Instead of swapping arguments on the stack, load them in reverse order
and jump further into bcopy (idea by kettenis@).
ok kettenis@
|
|
or the special value of 0.
ok deraadt@ otto@
|
|
ok otto@
|
|
related to man_term.c rev. 1.88, man_validate.c rev. 1.56.
|
|
reported by Nicolas Joly <njoly at pasteur dot fr>:
- add EOS spacing after trailing punctuation after .Cd, .Fc, and .Lb
- suppress spacing before trailing punctuation after .Fd
|
|
This fixes a problem where we could sleep for kva and then our pointers
would not be valid on the next pass through the loop. We do this
by adding buf_acquire_nomap() - which can be used to busy up the buffer
without changing its mapped or unmapped state. We do not need to have
the buffer mapped to invalidate it, so it is sufficient to acquire it
for that. In the case where we write the buffer, we do map the buffer, and
potentially sleep.
|
|
ok beck guenther
|
|
virtualbox).
Original patch by Dinar Talypov t.dinar.m AT gmail.com
Tweaks by brad@ and sf@
OK brad@
|
|
show them as a single word in the macro and _not_ as something
that looks like a function argument (i.e., with declarator).
ok beck@ schwarze@
|
|
variadic arguments passed in registers: these functions may pass a va_list to
another function, which will then need to rely upon a properly filled
__va_list struct and can't assume anything about the way arguments have been
passed to its caller.
|
|
|
|
|
|
|
|
them the "normal" command to configure bluetooth coexistence fails and
makes the firmware crash. Rename the IWN_FLAG_NO_BT_COEX flag and adjust some
comments to reflect this knowledge.
ok jcs@, mikeb@, mpi@
|
|
instead of causing a firmware crash, scanning now works.
Tested by Daniel Levai.
|
|
|
|
|
|
|
|
spelling fix;
|
|
modem and its Medion Mobile S4012 OEM version.
Developed and tested on Hardware provided by Katja Straube, thanks.
|
|
|
|
|
|
Correct EPERM vs EINVAL bits, mention posix and stack_t
ok miod@ beck@
|
|
See faq/current.html for more information.
The local_rcconf variable is not used anywhere anymore so drop it.
suggested by deraadt@
ok sthen@
|
|
spill the registers on __va_reg instead of calling move_block_from_reg().
|
|
ok ajacoutot@ and sthen@ on a previous version some time ago,
using the additional suggestion ".Dq NO" from jmc@.
|
|
Settle for "struct man *man", "struct mdoc *mdoc", "struct meta *meta"
and avoid the confusing "*m" which was sometimes this, sometimes that.
No functional change.
ok kristaps@ some time ago
|
|
of memory which will be used for the __va_reg register spill.
|
|
patch written by Nicolas Joly <njoly at pasteur dot fr>.
|
|
varagrs implementation being utterly wrong.
This is the same logic as the one I wrote for gcc 2.95, with a few more
optimizations whenever possible (such as not outputting instructions to fill
fields of the __va_list struct we know won't be accessed, now that we have
total control of the struct in the compiler).
It should now be possible to mix varags code compiled by gcc 2.95, with code
compiled with gcc 3, with the following exception: as I have finally found and
fixed the buglet causing all arguments to be passed on the stack if any of the
named arguments (before varargs) is a struct of 32 bytes or more passed by
value, such a (pretty uncommon) case will not be interoperable. One such case
can be found as va-arg-4.c in gcc's testsuite.
With these changes, all the following varargs exercizers from gcc's testsuite
now pass when compiled with the in-tree gcc 3:
gcc.c-torture/execute/920625-1.c
gcc.c-torture/execute/931004-10.c
gcc.c-torture/execute/931004-12.c
gcc.c-torture/execute/931004-14.c
gcc.c-torture/execute/931004-4.c
gcc.c-torture/execute/931004-6.c
gcc.c-torture/execute/931004-8.c
gcc.c-torture/execute/strct-varg-2.c
gcc.c-torture/execute/va-arg-1.c
gcc.c-torture/execute/va-arg-2.c
gcc.c-torture/execute/va-arg-4.c
gcc.c-torture/execute/va-arg-5.c
gcc.c-torture/execute/va-arg-6.c
as well as the few others of my own I had been using while working on gcc 2.95
more than 8 years ago.
|
|
|
|
This fixes the end of sentence spacing in open(2)
and in about 150 pages in the NetBSD base system.
Reported by Nicolas Joly <njoly a pasteur point fr>, merci!
|
|
The basic idea is to already pop the font at the end marker
instead of allowing it to linger until the final end of the block.
This requires a few preliminaries:
* For each block, save a pointer to the previous font
to be used in case the block breaks another and gets extended.
* That requires making node information writable during rendering.
* Now fonts may get popped in the wrong order; hence, after the stack
has already been rewound further by some block that began earlier,
ignore popping a font that was put on the stack later.
* To be able to exploit all this for font blocks, tie processing
to their body, not their block, which is more logical anyway.
Triggered by florian@ reporting vaguely similar issues with list blocks.
|
|
|
|
the interface index, hardware address, etc. as well as the interface
name.
|
|
intended.
|
|
|
|
* When allocating a body end marker, copy the pointer to the normalized
block information from the body block, avoiding the risk of subsequent
null pointer derefence.
* When inserting the body end marker into the syntax tree, do not try to
copy that pointer from the parent block, because not being a direkt child
of the block it belongs to is the whole point of a body end marker.
* Even non-callable blocks (like Bd and Bl) can break other blocks;
when this happens, postpone closing them out in the usual way.
|
|
|
|
i386 CD image also build/boot tested by todd@
ok mikeb@ deraadt@
|
|
AGP chipset is present. This will help if some quirks are needed.
ok mikeb@, kettenis@, miod@
|
|
if null_prologue(), i.e. if there is no stack frame to undo and no r1 to
restore.
Make the "epilogue" insn construct no longer depend on "return", but rather
on "(use (const_int 0))" as "prologue" and as generally done on other backends.
On the other hand, make it unconditionnal, instead of "! null_prologue()".
These changes make sure than a leaf procedure call does not end up "returning"
(i.e. jmp r1) upon return from the call, without restoring r1 and r30 (whenever
applicable) from the existing stack frame.
This makes a gcc3-compiled __main() (from libgcc2.c) no longer spin after
invoking the constructors, and gives the real payload (i.e. main() and whatever
follows from there) a chance to run.
|
|
string if not defined already, when cross-compiling. (curse words censored)
|
|
ok henning claudio benno
|
|
ok claudio@
|
