Skip to content
Snippets Groups Projects
  1. Oct 12, 1991
    • chiles's avatar
      · 6e7ae1ee
      chiles authored
      Documented some code someone added that was confusing.
      
      Added an optional argument to PRINT-FRAME-CALL-1, an internal function, to
      control whether it precedes its output with a newline.
      6e7ae1ee
    • chiles's avatar
      · c4e6ea59
      chiles authored
      The "Debug Breakpoint" and "Debug Delete Breakpoints" commands are ready for
      alpha testing, which they need a lot.  Some other bugs have been fixed too, but
      those were long enough ago, I don't remember them.
      c4e6ea59
    • chiles's avatar
      · 79304ca6
      chiles authored
      The latest alpha test breakpoint interface is available as described in the
      Debugging Tools Programmer's Interface.  Also, support for setting breakpoints
      from the editor has been changed to use the "WIRE" package directly.  There is
      a new interface for deleting breakpoints set by the editor.  This is all alpha
      test code.
      79304ca6
  2. Oct 08, 1991
  3. Oct 05, 1991
  4. Oct 04, 1991
  5. Oct 03, 1991
  6. Oct 02, 1991
    • ram's avatar
      Use CODE-TN instead of allocating a temporary in CODE, which is rather random, · 33dc8f2b
      ram authored
      and confuses the lifetime checker.
      33dc8f2b
    • ram's avatar
      In save-dynamic-state, init the NPF result even if there isn't any NFP. Might · 06c38186
      ram authored
      cause GC lossage, and confuses the assembly lifetime checker.
      06c38186
    • ram's avatar
      Changed (fixed?) argument/result parsing to default lifetimes, SCs and targets · 56d620ad
      ram authored
      from the inherited operand of the same name.  This eliminates the need for the
      inheriting VOP to respecify values that are really internal to the inherited
      VOP.
      56d620ad
    • chiles's avatar
      · 46a1b13a
      chiles authored
      Fixed lossage concerning the following compiler output:
         Definition has N args, but the previous definition had M.
      This used to be a note, but it should be a warning.
      
      If it is a warning that users change the definitions of structures, then it
      should be a warning when users change the definitions of functions.  In both
      cases, code might be lying around assuming an incorrect interface.  I think
      this is equally dangerous.  Also, changing the redefinition of arg counts to a
      warning makes it more compatible with the warning that someone supposedly
      called a routine with the wrong number of args.
      46a1b13a
  7. Oct 01, 1991
Loading