summaryrefslogtreecommitdiff
path: root/devel/libatomic_ops
diff options
context:
space:
mode:
authorepg <epg>2008-12-22 18:06:00 +0000
committerepg <epg>2008-12-22 18:06:00 +0000
commita71c40ee60c63b8084f1b412449168f7ded0f9be (patch)
treec4cac5a66fe7573bf43fa9005505d41c737339b4 /devel/libatomic_ops
parent63bf06f5b1a16fb1933722dc541381a980d1c8be (diff)
downloadpkgsrc-a71c40ee60c63b8084f1b412449168f7ded0f9be.tar.gz
s/ia/is/
Diffstat (limited to 'devel/libatomic_ops')
-rw-r--r--devel/libatomic_ops/DESCR2
1 files changed, 1 insertions, 1 deletions
diff --git a/devel/libatomic_ops/DESCR b/devel/libatomic_ops/DESCR
index 05f1f25f95a..772f9b6e0d2 100644
--- a/devel/libatomic_ops/DESCR
+++ b/devel/libatomic_ops/DESCR
@@ -5,7 +5,7 @@ atomic memory operations. These might allow you to write code:
- Makes more effective use of multiprocessors by allowing you to write
clever lock-free code. Note that such code is very difficult to get
right, and will unavoidably be less portable than lock-based code. It
- ia also not always faster than lock-based code. But it may occasionally
+ is also not always faster than lock-based code. But it may occasionally
be a large performance win.
- To experiment with new and much better thread programming paradigms, etc.