diff options
| author | shyouhei <shyouhei@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2010-10-25 07:57:51 +0000 |
|---|---|---|
| committer | shyouhei <shyouhei@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2010-10-25 07:57:51 +0000 |
| commit | a6ed06e51306ffe7311640040dade563419cb953 (patch) | |
| tree | 72a65e4ca295351b30be4675bf851350dcca6573 | |
| parent | 2c770d676c4089d7f57abb9ed885d3e458ba6b39 (diff) | |
ispell.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@29590 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
| -rw-r--r-- | ChangeLog | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -1,8 +1,8 @@ Mon Oct 25 16:38:07 2010 URABE Shyouhei <shyouhei@ruby-lang.org> * signal.c (rb_atomic_t): GCC (of at least recent versions) - has ubiquitos support for atomic operations. On that - compiler a C program can isse a memory barrier using these + has ubiquitous support for atomic operations. On that + compiler a C program can issue a memory barrier using these dedicated instructions. According to the GCC manual they cargo culted this feature form the Itanium ABI so chances are that other compilers could also support this feature. |