summaryrefslogtreecommitdiffstats
path: root/tools
Commit message (Collapse)AuthorAgeFilesLines
* Fix typo.ed2010-06-101-1/+1
| | | | Spotted by: Garrett Cooper
* This should be commented out.ed2010-06-091-1/+1
|
* Add WITHOUT_CLANG file with a description.rdivacky2010-06-091-0/+2
| | | | Approved by: ed (mentor)
* Add the VHBA package. It is here in tools because it's really a testbed.mjacob2010-06-0815-0/+2352
| | | | | Sponsored by: Panasas MFC after: 1 month
* Rework tcpp output so that it generates a comma-delimited list of values,rwatson2010-06-064-43/+50
| | | | | | | | | optionally with a header if "-h" is passed. Toast CPU time measurement in the server for now. Remove -C and -T, since we now always report both connections/sec and Gb/sec. MFC after: 1 week Sponsored by: Juniper Networks
* Although we currently don't compile in CPU-pinning support by default,rwatson2010-06-055-29/+45
| | | | | | | add a -P to enable it if it were. MFC after: 1 week Sponsored by: Juniper Networks
* o The typo was intended as it stated in the comment. Revert last.maxim2010-06-041-1/+1
| | | | Spotted by: dfr
* o Makefile BSDfication.maxim2010-06-041-23/+17
| | | | | PR: misc/147461 (with my changes) Submitted by: Erik Cederstrand
* o Fix typo: .uudef -> .undef.maxim2010-06-041-1/+1
| | | | | PR: misc/147462 Submitted by: Erik Cederstrand
* Fix stuttering sequences and reverse rangesbrian2010-06-024-1/+44
| | | | | PR: 123635 Submitted by: Ulrich Spörlein, uqs at spoerlein dot net
* sh: Fix a crash if a heredoc was not properly ended and parsing continued.jilles2010-05-301-0/+5
| | | | | | | | | Example (in interactive mode): cat <<EOF && ) The next command typed caused sh to segfault, because the state for the here document was not reset. Like parser_temp, this uses the fact that the parser is not re-entered.
* sh: Change interaction of command substitution and here documents.jilles2010-05-302-0/+100
| | | | | | | | | | | | | | | | | If a command substitution contains a newline token, this no longer starts here documents of outer commands. This way, we follow POSIX's idea of the command substitution being a separate script more closely. It also matches other shells better and is consistent with newline characters in quotes not starting here documents. The extension tested in parser/heredoc3.0 ($(cat <<EOF)\ntext\nEOF\n) continues to be supported. In particular, this change allows things like cat <<EOF && echo `pwd` (a `` command substitution after a here document) which formerly silently used an empty file as the here document, because the EOF of the inner command "pwd" also forced an empty here document.
* sh: Recognize "--" in . and exec.jilles2010-05-282-0/+46
| | | | | | | | | | | | | | | | | | Although "--" historically has not been required to be recognized for certain special builtins that do not take options in POSIX, some other implementations recognize options for them, requiring scripts to use "--" or avoid operands starting with "-". Operands starting with "-" can be avoided with eval by prepending a space, and cannot occur with break, continue, exit, return and shift as they only take numbers, nor with times as it does not take operands. With . and exec, avoiding "-" is not so easy as it may require reimplementing the PATH search; therefore the current proposal for POSIX is to require recognition of "--" for them. We continue to accept other strings starting with "-" as operands to . and exec, and also "--" if it is alone to . (which would otherwise be invalid anyway).
* sh: Add some simple tests for ., exec and return from . script.jilles2010-05-283-0/+62
|
* Correct several nits/problems in the unix_close_race regression test.rwatson2010-05-271-10/+16
| | | | | Submitted by: Mikolaj Golub <to.my.trociny at gmail.com> MFC after: 3 days
* Add unix_close_race, a regresion test to catch ENOTCONN being returnedrwatson2010-05-262-0/+139
| | | | | | | | | | | | improperly from one of two instances of close(2) being called simultaneously on both ends of a connected UNIX domain socket. The test tool is slightly tweaked to improve failure modes, and while often does trigger the problem, doesn't do so consistently due to the nature of the race. PR: kern/144061 Submitted by: Mikolaj Golub <to.my.trociny@gmail.com> MFC after: 3 days
* Introduce a new build knob for Flattened Device Tree support.raj2010-05-251-0/+3
| | | | | Reviewed by: imp Sponsored by: The FreeBSD Foundation
* sh: Add some simplistic tests for the wait builtin.jilles2010-05-232-0/+38
|
* Add an option file for WITHOUT_MAN_UTILS to regenerate src.conf(5).jkim2010-05-201-0/+9
|
* mdoc: consistently spell our email addresses <foo@FreeBSD.org>uqs2010-05-191-1/+1
| | | | Reviewed by: ru
* mdoc: move CAVEATS, BUGS and SECURITY CONSIDERATIONS sections to theuqs2010-05-131-5/+5
| | | | | | | | | | | bottom of the manpages and order them consistently. GNU groff doesn't care about the ordering, and doesn't even mention CAVEATS and SECURITY CONSIDERATIONS as common sections and where to put them. Found by: mdocml lint run Reviewed by: ru
* sh: Fix pathname expansion with quoted slashes like *\/.jilles2010-05-111-0/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These are git commits 36f0fa8fcbc8c7b2b194addd29100fb40e73e4e9 and d6d06ff5c2ea0fa44becc5ef4340e5f2f15073e4 in dash. Because this is the first code I'm importing from dash to expand.c, add the Herbert Xu copyright notice which is in dash's expand.c. When pathname expanding *\/, the CTLESC representing the quoted state was erroneously taken as part of the * pathname component. This CTLESC was then seen by the pattern matching code as escaping the '\0' terminating the string. The code is slightly different because dash converts the CTLESC characters to backslashes and removes all the other CTL* characters to allow substituting glob(3). The effect of the bug was also slightly different from dash (where nothing matched at all). Because a CTLESC can escape a '\0' in some way, whether files were included despite the bug depended on memory that should not be read. In particular, on many machines /*\/ expanded to a strict subset of what /*/ expanded to. Example: echo /*"/null" This should print /dev/null, not /*/null. PR: bin/146378 Obtained from: dash
* sh: Add some simple testcases for pathname expansion.jilles2010-05-111-0/+61
|
* Fix error in comment.jilles2010-05-091-1/+1
|
* sh: Add some parser tests.jilles2010-05-093-0/+53
| | | | | | | case1.0 tests POSIX requirements and one more for keywords in case statements. The others test very special cases of command substitution. These also work on stable/8.
* Generate some tests for sh's case command from the fnmatch tests.jilles2010-05-094-1/+256
| | | | | I'm committing the generated files because I don't like a build dependency for the sh(1) tests, and they are small and will not change much.
* sh: Fix bug in assignment error test.jilles2010-05-091-2/+2
| | | | | The test failed if the command returned nonzero exit status, and it really should return that.
* sh: Apply locale vars on builtins, recognize LC_MESSAGES as a locale var.jilles2010-05-051-0/+133
| | | | | | | | | | | | | | | | This allows doing things like LC_ALL=C some_builtin to run a builtin under a different locale, just like is possible with external programs. The immediate reason is that this allows making printf(1) a builtin without breaking things like LC_NUMERIC=C printf '%f\n' 1.2 This change also affects special builtins, as even though the assignment is persistent, the export is only to the builtin (unless the variable was already exported). Note: for this to work for builtins that also exist as external programs such as /bin/test, the setlocale() call must be under #ifndef SHELL. The shell will do the setlocale() calls which may not agree with the environment variables.
* Fix typo in usage message. Add -n to the list of valid arguments.philip2010-04-301-2/+2
| | | | MFC after: 1 day
* Add a TestFloat based test suite for floating-point implementationsmarius2010-04-2441-0/+18426
| | | | | | | | | | | | currently supporting sparc64. After a `make depend all` there are three programs; testsoftfloat for testing against the SoftFloat in src/lib/libc/softfloat for reference purposes, testemufloat for testing the emulator source in src/lib/libc/sparc64/fpu and testfloat for testing with the installed libc. Support for other architectures can be added as needed. PR: 144900 Submitted by: Peter Jeremy
* Adjust a test case and make it more jump optimization neutral for JIT case.jkim2010-04-231-1/+1
|
* sh: Add some more tests for ${v#...} and ${v%...}.jilles2010-04-231-0/+46
| | | | These pass on stable/8 as well.
* Merge @176820, @176822, @177156 to tcpp from P4 to HEAD:rwatson2010-04-212-13/+39
| | | | | | | | | | | | | | | | Improve accuracy of connection data transfer math. Disable Nagle's algorithm to avoid delaying transfers of data -- will want to refine this to combine payload with header transfer, however. Now that we're running w/o Nagle, try to send the initial data burst with the header in a single TCP segment. Prefer %zu to %ju for size_t. MFC after: 1 week Sponsored by: Juniper, Inc.
* Dump the AR_PHY_TURBO register on the AR5416. This register holds 11nrpaulo2010-04-191-0/+1
| | | | | | configurations. Sponsored by: iXsystems, inc.
* sh: Add testcases for double-quotes within quoted ${var+-...} (non-POSIX).jilles2010-04-181-0/+44
| | | | | | POSIX leaves things like "${var+"word"}" undefined. We follow traditional ash behaviour here. Hence, these testcases also work on stable/8.
* sh: On startup of the shell, use PWD from the environment if it is valid.jilles2010-04-171-0/+24
| | | | | | | | | | | | | | | Unset PWD if it is incorrect and no value for it can be determined. This preserves the logical current directory across shell invocations. Example (assuming /home is a symlink): $ cd $ pwd /home/foo $ sh $ pwd /home/foo Formerly the second pwd would show the physical path (symlinks resolved).
* fnmatch: Fix bad FNM_PERIOD disabling if an asterisk has been seen.jilles2010-04-161-0/+1
| | | | | | | Example: fnmatch("a*b/*", "abbb/.x", FNM_PATHNAME | FNM_PERIOD) PR: 116074 MFC after: 1 week
* Add some tests for fnmatch(3).jilles2010-04-162-1/+336
| | | | MFC after: 1 week
* sh: Test that bogus values of PWD are not imported from the environment.jilles2010-04-111-0/+11
| | | | | | Current versions pass this test trivially by never importing PWD, but I plan to change sh to import PWD if it is an absolute pathname for the current directory, possibly containing symlinks.
* Fix comment about NANO_ARCH. It can be set now. Also add a warningimp2010-04-061-1/+4
| | | | | about how it confuses TARGET and TARGET_ARCH and the need to separate the two out into independent variables.
* sh: Add test for nested arithmetic substitution.jilles2010-04-041-0/+17
| | | | | Pre-r206145 sh changes nested arithmetic substitution to parentheses, which is not always correct, as exercised by this test.
* sh: Add test for some associativity in arithmetic.jilles2010-04-041-0/+20
|
* sh: Do tilde expansion in substitutions.jilles2010-04-031-0/+90
| | | | | | | | | | | | | This applies to word in ${v-word}, ${v+word}, ${v=word}, ${v?word} (which inherits quoting from the outside) and in ${v%word}, ${v%%word}, ${v#word}, ${v##word} (which does not inherit any quoting). In all cases tilde expansion is only attempted at the start of word, even if word contains spaces. This agrees with POSIX and other shells. This is the last part of the patch tested in the exp-run. Exp-run done by: erwin (with some other sh(1) changes)
* sh: Fix duplicate variable name in test.jilles2010-04-031-2/+2
|
* sh: Add some testcases for the working parts of tilde expansion.jilles2010-04-031-0/+56
|
* sh: Allow quoting pattern match characters in ${v%pat} and ${v#pat}.jilles2010-04-031-0/+55
| | | | | | | | Note that this depends on r206145 for allowing pattern match characters to have their special meaning inside a double-quoted expansion like "${v%pat}". PR: bin/117748 Exp-run done by: erwin (with some other sh(1) changes)
* sh: Fix various things about expansions:jilles2010-04-032-0/+48
| | | | | | | | | | | | | | | | | | | | * remove the backslash from \} inside double quotes inside +-=? substitutions, e.g. "${$+\}a}" * maintain separate double-quote state for ${v#...} and ${v%...}; single and double quotes are special inside, even in a double-quoted string or here document * keep track of correct order of substitutions and arithmetic This is different from dash's approach, which does not track individual double quotes in the parser, trying to fix this up during expansion. This treats single quotes inside "${v#...}" incorrectly, however. This is similar to NetBSD's approach (as submitted in PR bin/57554), but recognizes the difference between +-=? and #% substitutions hinted at in POSIX and is more refined for arithmetic expansion and here documents. PR: bin/57554 Exp-run done by: erwin (with some other sh(1) changes)
* sh: Add some testcases for the working parts of ${v%...} and ${v#...}.jilles2010-04-031-0/+85
|
* Two fixes:imp2010-03-311-15/+2
| | | | | | | | | | (1) We don't need a custom install_kernel. We can install without symbols by adding INSTALL_NODEBUG (which likely should be WITHOUT_KERNEL_SYMBOLS_FILE, or something shorter) to CONF_INSTALL (2) for make buildenv stage, use NANO_MAKE_CONF_BUILD rather than the non-existant NANO_MAKE_CONF. MFC after: 7 days
* Stop hard coding i386 as the arch for the build. Instead, default to theimp2010-03-311-1/+6
| | | | | | | | | | | processor we're running on. Also, supply amd64 version of create_diskimage that's the same as i386's. # didn't fix the confusion between using the processor for this and using # the machine (which would be more appropriate). NANO_ARCH smashes the two # together right now. MFC after: 7 days
OpenPOWER on IntegriCloud