summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndy Wingo <wingo@pobox.com>2013-01-15 19:11:24 +0100
committerAndy Wingo <wingo@pobox.com>2013-01-15 19:13:09 +0100
commit2fe300ae8d286e5c8e641dd08675d0a73c472b48 (patch)
tree7b695ad4977ab52563b8fe8fbf68438b4c667327
parentb071ce21474796c8a8b23599e67db88bd4716a76 (diff)
downloadguile-2fe300ae8d286e5c8e641dd08675d0a73c472b48.tar.gz
remove scm_is_pair gcc hack
* libguile/pairs.h (scm_is_pair): Remove the (crufty!) GCC workaround, as we no longer check the heap to see if something is a pair.
-rw-r--r--libguile/pairs.h21
1 files changed, 0 insertions, 21 deletions
diff --git a/libguile/pairs.h b/libguile/pairs.h
index 099d206e3..d9495486c 100644
--- a/libguile/pairs.h
+++ b/libguile/pairs.h
@@ -136,27 +136,6 @@ scm_cons (SCM x, SCM y)
SCM_INLINE_IMPLEMENTATION int
scm_is_pair (SCM x)
{
- /* The following "workaround_for_gcc_295" avoids bad code generated by
- i386 gcc 2.95.4 (the Debian packaged 2.95.4-24 at least).
-
- Under the default -O2 the inlined SCM_I_CONSP test gets "optimized" so
- the fetch of the tag word from x is done before confirming it's a
- non-immediate (SCM_NIMP). Needless to say that bombs badly if x is a
- immediate. This was seen to afflict scm_srfi1_split_at and something
- deep in the bowels of ceval(). In both cases segvs resulted from
- deferencing a random immediate value. srfi-1.test exposes the problem
- through a short list, the immediate being SCM_EOL in that case.
- Something in syntax.test exposed the ceval() problem.
-
- Just "volatile SCM workaround_for_gcc_295 = lst" is enough to avoid the
- problem, without even using that variable. The "w=w" is just to
- prevent a warning about it being unused.
- */
-#if defined (__GNUC__) && __GNUC__ == 2 && __GNUC_MINOR__ == 95
- volatile SCM workaround_for_gcc_295 = x;
- workaround_for_gcc_295 = workaround_for_gcc_295;
-#endif
-
return SCM_I_CONSP (x);
}