summaryrefslogtreecommitdiff
path: root/lzo/BUGS
diff options
context:
space:
mode:
authorArne Schwabe <arne@rfc2549.org>2012-07-02 21:42:07 +0200
committerArne Schwabe <arne@rfc2549.org>2012-07-02 21:42:07 +0200
commit21c3e54010129b504891e1786bf425d89328c969 (patch)
tree2e3eba26f5f0fa454188e1b52c7cab3761c4f208 /lzo/BUGS
parentd4a1b52faa85df4446560a48c6bcc57f016e0c3c (diff)
parentb42eacfa8da0a642d629714f188cc0fc4c7e601a (diff)
Merge
Diffstat (limited to 'lzo/BUGS')
-rw-r--r--lzo/BUGS8
1 files changed, 4 insertions, 4 deletions
diff --git a/lzo/BUGS b/lzo/BUGS
index e1aa2a7d..aed77990 100644
--- a/lzo/BUGS
+++ b/lzo/BUGS
@@ -7,15 +7,15 @@ LZO is free of any known bugs.
Nevertheless LZO has been reported to break the optimizer of some
compilers including gcc 2.7.2 (AIX, IRIX) and Watcom C 9.5.
-So if `lzotest' reports data decompression errors you should recompile
+So if 'lzotest' reports data decompression errors you should recompile
everything without optimizations and see if that fixes the problem.
I'd like to hear about optimizer problems and possible workarounds.
Known compiler problems:
------------------------
- some versions of gcc use `-O2 -fno-strength-reduce'
- some versions of gcc use `-O2 -fno-schedule-insns -fno-schedule-insns2'
- Watcom C 9.5 compile with `-oneax' instead of `-oneatx'
+ some versions of gcc use '-O2 -fno-strength-reduce'
+ some versions of gcc use '-O2 -fno-schedule-insns -fno-schedule-insns2'
+ Watcom C 9.5 compile with '-oneax' instead of '-oneatx'