jgr == Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com
writes:
jgr Here is the problem: char in Linux is signed char, while in OS X it
jgr seems to default to unsigned char. I have changed ECL so that BASE-CHAR
jgr objects are unboxed using the explicit C type unsigned char
Eric Marsden eric.mars...@free.fr writes:
jgr == Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com
writes:
jgr Here is the problem: char in Linux is signed char, while in OS X it
jgr seems to default to unsigned char. I have changed ECL so that
BASE-CHAR
jgr objects are
On Tue, Nov 22, 2011 at 10:47 AM, Stas Boukarev stass...@gmail.com wrote:
I don't see how that's a bug, b isn't required to be EQL to b. It
can be, especially when coalesced by the compiler, but the reader
usually constructs a new string each time.
I agree. Compare that with
(lambda (a)
jgr == Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com
writes:
jgr I agree. Compare that with
Indeed, insufficient thinking on my part, sorry.
--
Eric Marsden
--
All the data continuously
On Sun, Nov 13, 2011 at 7:18 PM, Eric Marsden eric.mars...@free.fr wrote:
,
| (disassemble '(lambda (p1 p2) (declare (optimize (safety 0)) (type
(member #\U00FE) p2)) (equalp p1 p2)))
|
| ;;; Compiling (DEFUN C::GAZONK ...).
| ;;; Emitting code for C::GAZONK.
| /*function
jgr == Juan Jose Garcia-Ripoll juanjose.garciarip...@googlemail.com
writes:
jgr This will give us a clue about the quality of the generated code -- I am
jgr asking because in my OS X it looks just fine.
Here is the result of attaching gdb.
,
| Program received signal SIGSEGV,
On Sat, Nov 12, 2011 at 12:47 PM, Eric Marsden eric.mars...@free.fr wrote:
The following transcript illustrates a bug (on Linux/AMD64) when
compiling code with low safety and type declarations involving unicode
characters.
A few things would be helpful
- Configuration flags for ECL
- Value
On Sun, Nov 13, 2011 at 7:06 PM, Eric Marsden eric.mars...@free.fr wrote:
The bytecode disassembly of my function is below. However, the function
works fine when byte-compiled, only segfaulting when using the C
compiler. I haven't managed to obtain disassembly when compiled via C.
Sorry,
