Re: [Gcl-devel] Re: interrupts in 64-bit GCL

[Camm Maguire]

Greetings!  You can see the gcc flags emitted with

(trace si::system)

I think the current behavior is

(proclaim '(optimize debug))

Warning:
The OPTIMIZE quality DEBUG is unknown.
NIL

in 2.6.8 and a no-op in 2.7.0, though it should be fixed in the
latter. 

Take care,

Gabriel Dos Reis <address@hidden> writes:

> Camm Maguire <address@hidden> writes:
>
> | Greetings!  I suspect a missing signal block around some code that
> | needs protecting.  I've reprodced under gdb, but there are no
> | debugging symbols in the image.  [ Question for list -- have computers
> | now become so fast that -g should be included by default in all gcl
> | images? It used to slow down the compiler, don't know about now.  It
> | does make the image quite a bit bigger. ]
>
> I'm not sure what it the relation between -g and
>
>     (proclaim '(optimize debug))
>
> but I can report that with GCL-based OpenAxiom, the build is really
> slow and the resulting system runs very slow, even on my fastest 
> quad-core machines.
>
> -- Gaby
>
>
>
>

-- 
Camm Maguire                                        address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah