Dusting off my POPLOG version of C I found that on Linux it gave a baffling
stack underflow
!> isFloat <Int TQ_int:[] Sign_int:<false> Size_int:<false>>
;;; MISHAP - ste: STACK EMPTY (missing argument? missing result?)
;;; FILE : /user/pooh/users1/pop/local/C/test.c LINE NUMBER: 2129
;;; DOING : mishap_GDB Relink_isa UnlinkedIsa Compile_divide Compile(Appli
;;; cation,_) Example preprocessor_command top_level_declaration translati
;;; on_unit call_parse_gen compile_c c_compile runproc charin proc_tok
;;; null parse_and_pr_statement call_parse_gen c_compile_statement
;;; C_reset pop_setpop_compiler
Type of error = Statement_RT
!X isFloat
X Compile_divide
Not this is NOT an error in lib objectclass as I at first thought,
but seems to be another instance of the peculiar behaviour of the
stack in Linux Poplog (for example the problem disappears if
I try compiling the same C expression more deeply embedded).
Is their a simple recipe for rebuilding Linux Poplog with a bigger
stack?
Robin.
|