- Aug 10, 2012
-
-
Raymond Toy authored
src/lisp/gencgc.c: * Move the macros for fpu buffers from gencgc.c to here. src/lisp/x86-arch.c: * Use the new save_fpu_state instead of fpu_save. And apply to all OSes.
-
- Jan 04, 2012
-
-
Raymond Toy authored
match the sa_sigaction argument types. Adjust code appropriately to use os_context_t appropriately too.
-
- Nov 04, 2011
-
-
Raymond Toy authored
-
- Dec 26, 2010
-
-
rswindells authored
registers. The test is a stub on everything except NetBSD for now.
-
- Dec 23, 2010
-
-
rtoy authored
-
rtoy authored
working when tracing, for example (declaim (ftype (function (double-float) double-float) fact)) (defun fact (x) (declare (double-float x)) (if (= x 1) 1d0 (* x (fact (1- x))))) lisp/x86-lispregs.h o NetBSD has access to the eflags register lisp/x86-arch.c: o Add some debugging prints (disabled). o The stuff near line 262 about pc-9 pointing to the pushf instruction should be conditioned on SC_EFLAGS because that's what decides whether we insert the pushf instructions for single stepping.
-
- Dec 22, 2010
-
-
rtoy authored
Solaris/x86. There should be no functional changes for either other x86 ports or for the sparc port.
-
- Jan 06, 2009
-
-
rtoy authored
-
- Dec 07, 2008
-
-
agoncharov authored
-
- Nov 12, 2008
-
-
rtoy authored
sse2-packed-2008-11-12).
-
- Mar 19, 2008
-
-
cshapiro authored
void keyword to specify empty parameter lists.
-
- Jan 28, 2008
-
-
rtoy authored
array. The new function returns 2 new output values. code/irrat.lisp: o Rename the original %ieee754-rem-pi/2 to %%ieee754-rem-pi-2. o Define the new %ieee754-rem-pi/2 function. This returns the output as two output values instead of an array. o Use the new function. We should have wrapped the original with without-gcing, but we don't have to anymore. lisp/ppc-arch.c: lisp/x86-arch.c: o Implement the new C interface to __ieee754_rem_pio2 lisp/Config.linux_gencgc: o Use -ffloat-store when compiling e_rem_pio2.c and k_rem_pio2.c, just to be sure.
-
- Dec 15, 2007
-
-
rtoy authored
x86-lispregs.h: o Add SC_EFLAGS macro to access the eflags register (currently only for linux and darwin). x86-arch.c: o Use the SC_EFLAGS macro to enable/disable single-stepping. o If SC_EFLAGS is not defined, use the single-step helper stuff.
-
rtoy authored
issues like why the mcontext slot is 0 in the sigcontext from a function end breakpoint. This works around that problem for now. lisp/x86-arch.c: o Add documentation on how arch_do_displaced_inst works. o Darwin has the eflags register in the sigcontext so use that to enable and disable single-stepping using the eflags slot. This is how Linux works too. This change makes function start breakpoints work. code/debug-int.lisp: o In FIND-ESCAPED-FRAME, make sure the mcontext slot is not null (0) before we try to grab the cfp slot from it. This works around an issue where the mcontext slot is 0 on Darwin. code/ntrace.lisp: o Make *TRACE-ENCAPSULATE-DEFAULT* be :default again.
-
- Dec 14, 2007
-
-
cshapiro authored
sigcontext before calling back into Lisp. The rounding mode is always set correctly when we reenter Lisp through call_into_lisp. We now ensure that the trap bits enabled by the user are also preserved.
-
- Dec 03, 2007
-
-
pwerkowski authored
-
- Nov 16, 2007
- Jul 25, 2007
-
-
cshapiro authored
sigset_t is different from the one used in the Linux kernel. This means that we cannot make assignments of sigset_t objects without corrupting memory. To work around this problem we update uc_sigmask differently on Linux than on other systems. Also, remove x87 control word updates since the x87 is setup correctly inside call_into_lisp.
-
- Jul 15, 2007
-
-
cshapiro authored
-
- Jul 06, 2007
-
-
cshapiro authored
-
- Oct 06, 2005
-
-
rtoy authored
"invalid lvalue". From Rex Dieter, cmucl-imp, 2005/10/06.
-
- Sep 15, 2005
-
-
rtoy authored
.indent.pro.
-
- Jul 08, 2004
-
-
rtoy authored
* gencgc.c: o fixup up fprintf warnings o generation_bytes_allocated() defined only when GC_ASSERTIONS is #defined. * x86-arch.c: fixup printf warnings.
-
- Jul 07, 2004
-
-
rtoy authored
-
- May 18, 2004
-
-
cwang authored
-
- Oct 24, 2003
-
-
toy authored
* x86-assem.S (multiple_value_return): Add new functions to handle heap overflow warnings and errors. * x86-arch.c (sigtrap_handler): Add cases for the two new heap overflow traps. * interrupt.c (interrupt_handle_space_overflow): Add support for x86. * parms.lisp (static-symbols): Add new static symbols for heap overflow checking. Add new trap types for heap overflow checking.
-
- Nov 02, 2002
-
-
toy authored
-
- Aug 28, 2002
-
-
pmai authored
o Conditionalized some code that is only used in linkage-table builds on :linkage-table and LINKAGE_TABLE respectively. o Modernized undefined_ff_tramp based on recent changes, and renamed it to undefined_foreign_symbol_trap, because it really isn't a trampoline. o Conditionalized a stray puts(...,dlerror()) in Linux-os.c on DEBUG o Installed an error reporter for UNDEFINED_FOREIGN_SYMBOL_ERROR, which for now signals a simple-program-error. We might want to introduced a new condition UNDEFINED-FOREIGN-SYMBOL or something, which could also be used by the old foreign linkage code.
-
- Aug 27, 2002
-
-
moore authored
On x86 FreeBSD and Linux, change the way foreign symbol addresses are resolved. They now go through a table -- effectively a new space in the core file. Function references are resolved lazily, data references are resolved on startup and when a .so is loaded. The end result is that cores can be dumped that contain references to symbols in shared libraries. Also, the dependence of the core on addresses in the Lisp runtime is broken. The linkage table feature is controlled by :linkage-table and LINKAGE_TABLE in C runtime. Several foreign symbols are now Lisp static symbols, so a cross compile is required whether or not the new stuff is used. I've checked in boot4-cross-foreign-linkage.lisp that builds the compiler for linkage table; do whatever you usually do for the non-linkage table case:) Seriously, lets start a discussion on standardizing "cross compilation," not to mention the general build procedure.
-
- Jan 28, 2002
-
-
pmai authored
was already cleaned up with the OpenBSD port, this doesn't require massive changes. Since current NetBSD is ELF-based by default, we don't make use of the ELF feature, or in other words: The presence of the NetBSD feature implies ELF, since there is no support for non-ELF NetBSD.
-
- Dec 06, 2001
-
-
pmai authored
code which were previously conditionalized on :FreeBSD, are now conditionalized on :BSD instead, with the :BSD feature now implying a 4.4BSD(lite2) derived OS. This should make future BSD-ports easier. FreeBSD and OpenBSD are differentiated by having either :FreeBSD or :OpenBSD on the features list. Currently the OpenBSD port does not have working ELF support, because OpenBSD 2.9 is still non-ELF by default. So don't put ELF on the features list when building for OpenBSD, or fix the code to work correctly in this case instead.
-
- Oct 27, 2000
-
-
dtc authored
-
- Oct 21, 2000
-
-
dtc authored
may not be a fpstate in some rare cases.
-
- Sep 05, 2000
-
-
dtc authored
-
- Nov 11, 1999
-
-
dtc authored
otherwise the set of masked exceptions may be lost. Further, when restoring the FPU control word restore the rounding mode to its required default of round-to-nearest.
-
- Feb 19, 1998
- Nov 30, 1997
-
-
dtc authored
-
- Nov 25, 1997
-
-
dtc authored
-