Age | Commit message (Collapse) | Author |
|
|
|
- Additionally, test _setjmp and sigsetjmp as implementations are different.
|
|
preserved by setjmp. Currently under REGRESS_FULL as this fails
on certain archs.
|
|
- adjust gcc-builtins to use the same approach as gcc-bounds
- enable gcc-bounds and gcc-builtins in the default regression suite
now that everything passes
|
|
actually shows the security warning. Also add some other cases
where GCC used to yield the warning but shouldn't (e.g. strncat
simplified into strcat).
|
|
|
|
|
|
|
|
|
|
Following an idea from Franco Fichtner, but implemented more cleanly.
This reduces groff-mandoc-differences in base by a fantastic 7.5%.
|
|
|
|
but only within .Nm blocks. Simplify the code accordingly.
This reduces groff-mandoc differences in base by about 2%.
Triggered by research done by Franco Fichtner.
|
|
we have to compare the line where the first one *ends* (not where it begins)
to the line where the second one starts.
This fixes the bug that .Bk allowed output line breaks right after block
macros spanning more than one input line, even when the next macro follows
on the same line.
|
|
|
|
that inadvertently disabled the -Tman tests. Oops.
Enable them again.
Fortunately, in the meantime, nothing slipped.
|
|
Patch from Franco Fichtner <franco at lastsummer dot de>.
|
|
Improves cvs(1) pcap-filter(3) readline(3) termcap(5) cvsbug(8)
mkhybrid(8) nsd-zonec(8) in multiple places and c++filt(1) com_err(3)
nsd_conf(5) term(5) nsdc(8) in one place each.
Reduces overall groff-mandoc-differences in base by about 1.5%.
Patch from Franco Fichtner <franco at lastsummer dot de> (DragonFly).
|
|
what we did for gcc3.
|
|
|
|
hardware.
|
|
|
|
|
|
|
|
For a long time, we handle this in roff(7) and man(7) macros.
Now add correct handling for the mdoc(7) case, too.
Closely based on a patch by Tsugutomo dot ENAMI at jp dot sony dot com,
see http://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=48438
received via Thomas Klausner (wiz@), slightly tweaked by me.
|
|
the first non-digit character. While here, implement and document
an optional sign, requesting increment or decrement, as documented
in the Ossanna/Kernighan/Ritter troff manual and supported by groff.
Reported by bentley@ on discuss at mdocml.
|
|
|
|
|
|
use TAILQ_*_SAFE more than might be needed.
Bulk ports build by sthen@ showed nobody sticking their fingers
so deep into the kernel.
Feedback and suggestions from millert@. ok jsing@
|
|
encryption ciphers instead of specifying them manually; ensures that
the new chacha20poly1305@openssh.com mode is tested;
ok markus@ and naddy@ as part of the diff to add
chacha20poly1305@openssh.com
|
|
on some systems portable OpenSSH is built on.
|
|
|
|
|
|
to successfully run this; ok djm@
|
|
As header scanning is back, there is always a icmp6 parameter problem
response. Add tests that hide the routing header behind an atomic
fragment header to get the RFC 5095 behaviour. One test puts the
routing header into the second fragment so that it cannot be detected
without reassembly.
|
|
|
|
are configured correctly. Add a scapy test that creates a packet
without routing header to check the setup.
|
|
close below-subsection implicit scopes that may still be open.
In the formatter, make sure indentation is reset when leaving a scope,
not only when entering the next one.
Improves the formatting of gpg(1); issue reported by jca on ports.
|
|
|
|
It is already documented in the Heirloom troff manual,
and groff handles it as well.
Bug reported by Bjarni Ingi Gislason <bjarniig at rhi dot hi dot is>
on <bug-groff at gnu dot org>. Well, admittedly, that bug was reported
against groff, but mandoc was even more broken than groff with respect
to this syntax...
|
|
|
|
New per-directory variables UTF8_TARGETS and SKIP_ASCII,
intended as subsets of REGRESS_TARGETS.
New .PHONY targets "utf8" and "utf8-clean" to only do -Tutf8 tests;
of course, "all" and "clean" also include this functionality.
While here, prefix internal variables with an underscore.
|
|
|
|
where necessary for a specific test.
|
|
|
|
|
|
|
|
|
|
|
|
the GCM ciphers.
|
|
|