diff options
| -rw-r--r-- | ChangeLog | 6 | ||||
| -rw-r--r-- | baseboards/mcore-moto-sim.exp | 4 | ||||
| -rw-r--r-- | lib/dejagnu.exp | 4 | ||||
| -rw-r--r-- | lib/dg.exp | 4 | ||||
| -rw-r--r-- | lib/dmucs.exp | 2 | ||||
| -rw-r--r-- | lib/framework.exp | 4 | ||||
| -rw-r--r-- | lib/remote.exp | 2 | ||||
| -rw-r--r-- | lib/target.exp | 4 | ||||
| -rw-r--r-- | runtest.exp | 6 |
9 files changed, 21 insertions, 15 deletions
@@ -1,5 +1,11 @@ 2016-03-30 Ben Elliston <bje@gnu.org> + * baseboards/mcore-moto-sim.exp, lib/dejagnu.exp, lib/dg.exp, + lib/dmucs.exp, lib/framework.exp, lib/remote.exp, lib/target.exp, + runtest.exp: Fix spelling errors in comments. + +2016-03-30 Ben Elliston <bje@gnu.org> + * lib/remote.exp (remote_expect): Use perror not send_user. 2016-03-29 Ben Elliston <bje@gnu.org> diff --git a/baseboards/mcore-moto-sim.exp b/baseboards/mcore-moto-sim.exp index e0321b0..42390f0 100644 --- a/baseboards/mcore-moto-sim.exp +++ b/baseboards/mcore-moto-sim.exp @@ -18,9 +18,9 @@ # Inc., 51 Franklin Street - Fifth Floor, Boston, MA 02110-1301, USA. # This is a HACKED version of mcore-sim.exp that is intended to -# support running tests on Motorola's proprietry MCore simulator. +# support running tests on Motorola's proprietary MCore simulator. -# It is quite likely that thia file will need to be modified in +# It is quite likely that this file will need to be modified in # order for you to use Motorola's simulator. # This is a list of toolchains that are supported on this board. diff --git a/lib/dejagnu.exp b/lib/dejagnu.exp index 732bdf9..f760d8d 100644 --- a/lib/dejagnu.exp +++ b/lib/dejagnu.exp @@ -98,8 +98,8 @@ proc host_compile {compline} { return ${comp_output} } -# Execute the executable file, and anaylyse the output for the -# test state keywords. +# Execute the executable file, and analyse the output for the test +# state keywords. # Returns: # A "" (empty) string if everything worked, or an error message # if there was a problem. @@ -115,7 +115,7 @@ # pattern matching. This also gives the tool an opportunity to review # the output and check for any conditions which indicate an "untested" # or "unresolved" state. An example is if a testcase is too big and -# fills all available ram (which can happen for 16 bit cpus). The +# fills all available ram (which can happen for 16 bit CPUs). The # result is either the pruned text or # "::untested|unresolved|unsupported::message" # (eg: "::unsupported::memory full"). @@ -564,7 +564,7 @@ proc dg-runtest { testcases options default-extra-options } { # dg-trim-dirname -- rip DIR_NAME out of FILE_NAME # # Syntax: dg-trim-dirname dir_name file_name -# We need to go through this contorsion in order to properly support +# We need to go through this contortion in order to properly support # directory-names which might have embedded regexp special characters. # proc dg-trim-dirname { dir_name file_name } { diff --git a/lib/dmucs.exp b/lib/dmucs.exp index 9c5fbfa..9038b0b 100644 --- a/lib/dmucs.exp +++ b/lib/dmucs.exp @@ -17,7 +17,7 @@ # Inc., 51 Franklin Street - Fifth Floor, Boston, MA 02110-1301, USA. # This file requires a slightly modified dmucs, which has been -# modified to support mutiple architectures for toolchain +# modified to support multiple architectures for toolchain # testing. DMUCS sends the CPU load to a server, which we can query # using the 'gethost' command to get the next available slave for a # remote test based on which one is the least busy. The code for this diff --git a/lib/framework.exp b/lib/framework.exp index 29a813e..6bec958 100644 --- a/lib/framework.exp +++ b/lib/framework.exp @@ -174,7 +174,7 @@ proc is_remote { board } { return 1 } -# If this is a canadian (3 way) cross. This means the tools are +# If this is a Canadian (3 way) cross. This means the tools are # being built with a cross compiler for another host. # proc is3way {} { @@ -484,7 +484,7 @@ proc setup_xfail { args } { # # A bug report ID _MUST_ be specified, and is the first argument. # It still must be a string without '-' so we can be sure someone -# did not just forget it and we end-up using a taget triple as +# did not just forget it and we end-up using a target triple as # bug id. # # Multiple target triplet patterns can be specified for targets diff --git a/lib/remote.exp b/lib/remote.exp index c88e5bb..043368b 100644 --- a/lib/remote.exp +++ b/lib/remote.exp @@ -1167,7 +1167,7 @@ proc standard_wait { dest timeout } { return [list $status $output] } -# This checks the value cotained in the variable named "variable" in +# This checks the value contained in the variable named "variable" in # the calling procedure for output from the status wrapper and returns # a non-negative value if it exists; otherwise, it returns -1. The # output from the wrapper is removed from the variable. diff --git a/lib/target.exp b/lib/target.exp index 4c73c61..0cc6422 100644 --- a/lib/target.exp +++ b/lib/target.exp @@ -64,14 +64,14 @@ proc push_target { name } { push_config target $name } -# Set the host connnection. +# Set the host connection. # proc push_host { name } { pop_config host push_config host $name } -# Set the build connnection. +# Set the build connection. # proc push_build { name } { pop_config build diff --git a/runtest.exp b/runtest.exp index 69d2f79..f7476c8 100644 --- a/runtest.exp +++ b/runtest.exp @@ -668,12 +668,12 @@ if { $arg_build_triplet != "" } { set build_triplet $arg_build_triplet } -# if we only specify --host, then that must be the build machne too, and we're -# stuck using the old functionality of a simple cross test +# If we only specify --host, then that must be the build machine too, +# and we're stuck using the old functionality of a simple cross test. if {[expr { $build_triplet == "" && $host_triplet != "" } ]} { set build_triplet $host_triplet } -# if we only specify --build, then we'll use that as the host too +# If we only specify --build, then we'll use that as the host too. if {[expr { $build_triplet != "" && $host_triplet == "" } ]} { set host_triplet $build_triplet } |