Description: 修复 SBCL 2.6.0 编译器崩溃导致的 amd64 构建失败
 SBCL (>= 2.6.0) 的保守 CAR/CDR 类型推导（LVAR-CONSERVATIVE-TYPE）在
 编译 rengine.lisp 时因 term-memo-get-normal-form 内联展开中的多值 LVAR
 触发 SB-C::NODE-CONSERVATIVE-TYPE TYPE-ERROR（值为非 SB-C::VALUED-NODE 的
 列表），导致 dumps/sbcl/cafeobj.sbcl 目标编译中止。移除该函数的 INLINE
 声明使内联展开不再合并多分支引用，规避编译器缺陷；函数仍以
 (SPEED 3) (SAFETY 0) 编译，调用开销相对哈希表查询与项重写可忽略。
Author: tangxiaofeng <tangxiaofeng@kylinos.cn>
Origin: other
Forwarded: not-needed
Last-Update: 2026-08-31

--- cafeobj-1.6.0.orig/chaos/cafein/rengine.lisp
+++ cafeobj-1.6.0/chaos/cafein/rengine.lisp
@@ -971,7 +971,18 @@
              (normalize-term term))))))))
 
 ;;;
-(declaim (inline term-memo-get-normal-form))
+;; NOTE: Do NOT inline this function.  The SBCL (>= 2.6.0) compiler crashes
+;; (TYPE-ERROR, value is not of type SB-C::VALUED-NODE, raised inside
+;; SB-C::NODE-CONSERVATIVE-TYPE) while compiling the inline expansion when the
+;; (IF NORMAL-FORM NORMAL-FORM (PROGN ... TERM)) result, whose two branch REFs
+;; merge into one LVAR, is consumed by (CAR ...) after inlining into
+;; NORMALIZE-TERM (the new conservative CAR/CDR type derivers call
+;; LVAR-CONSERVATIVE-TYPE, which walks the CAST use and hits the multi-use
+;; LVAR).  Dropping the INLINE declaration keeps the system buildable; the
+;; function is still compiled with (SPEED 3) (SAFETY 0) and the call overhead
+;; is negligible compared with the hash-table lookups and term reduction it
+;; performs.
+;; (declaim (inline term-memo-get-normal-form))
 (defun term-memo-get-normal-form (term strategy)
   (declare (type term term)
            (type list strategy)
