Custom Query (1030 matches)

We made a change to support "large" functions (those with 64K or more 32-bit words of code/immediate data) on x8632 by changing the interpretation of the 16-bit word which precedes the function entry point (high bit clear -> count of "code" words in low 15 bits, high bit set -> count of "node" words in low 15 bits.) We missed a case in relocate_area_contents(), which is used to handle the case where a heap image can't be mapped into the address from which it was saved.

A development version of ACL2 both created at least one "large" function and was saved from a non-canonical address (for unknown reasons) and exposed this problem.

We never actually load the ELF file used to provide symbolic information for opreport on Linux, but (just in case ...) set the flags in the "lisp" section in which those symbols are defined to indicate that the section shouldn't be loaded into memory.

In oprofile 0.9.5, symbols defined in sections that aren't loaded are ignored by opreport. (oprofile 0.9.5 was released on 2009-07-31 and is present in Fedora 11 and Ubuntu 9.10, at least.)

(reported on #ccl)

(defstruct (foo (:constructor make-foo (&aux x)))
  (x nil :type fixnum))

(make-foo) ; shouldn't signal a TYPE-ERROR, per bizarre nonsense in 3.4.6