diff options
| author | nobu <nobu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2015-12-02 02:36:58 +0000 |
|---|---|---|
| committer | nobu <nobu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2015-12-02 02:36:58 +0000 |
| commit | 97fe401413ca7f98f29d043d2d6dd8c672030b11 (patch) | |
| tree | b25a05e6720ca4a5300737710c362f0f7382e57a | |
| parent | aed0db8bd35af72f15514c747d8a64737192c6b8 (diff) | |
explicit_bzero.c: fix typos
* missing/explicit_bzero.c (explicit_bzero): fix typos, probably.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@52849 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
| -rw-r--r-- | missing/explicit_bzero.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/missing/explicit_bzero.c b/missing/explicit_bzero.c index db66eeeb9d..2409deca20 100644 --- a/missing/explicit_bzero.c +++ b/missing/explicit_bzero.c @@ -64,9 +64,9 @@ void explicit_bzero(void *b, size_t len) { /* - * volatile is not enough if compiler have a LTO (link time + * volatile is not enough if the compiler has an LTO (link time * optimization). At least, the standard provides no guarantee. - * However, gcc and major other compiler never optimize a volatile + * However, gcc and major other compilers never optimize a volatile * variable away. So, using volatile is practically ok. */ volatile char* p = (volatile char*)b; |