For the record, the way we did in QRes was to proclaim appropriate
system-dependent settings in some perform :around methods
Look for proclaim in quux/lisp/qres-build/qres-build.lisp and
quux/lisp/qres-build/enhance-asdf.lisp
in the released quux tarball.
—♯ƒ • François-René ÐVB Rideau •Reflection
Managing scoped optimizations seems like something that should be at least
partly handled by a CDR, if anyone pays any attention to those.
It would be great if there was an expression, common to most CL
implementations, that we could wrap around a call to COMPILE-FILE in order to
impose an opti
On Wed, 2014-03-19 at 17:22 -0500, Robert Goldman wrote:
> Robert Brown wrote:
> > Does ASDF set compiler optimization settings before compiling
> > each file when building? I'm concerned that changing the
> > optimization setting inside one source file could cause the
> > change to stick and be u
Here's the problem I want solved. A library author wants to
compile some source files with high optimization settings. How
can this be done? The author could put
(declaim (optimize ... ))
at the top of those files, but then any code compiled later may
accidentally get the new settings. If
Robert Brown wrote:
> Does ASDF set compiler optimization settings before compiling
> each file when building? I'm concerned that changing the
> optimization setting inside one source file could cause the
> change to stick and be used for other files. I don't think the
> CL standard mandates that
On Wed, Mar 19, 2014 at 5:54 PM, Robert Brown wrote:
> Does ASDF set compiler optimization settings before compiling
> each file when building?
Not by default, though you can teach it to.
> I'm concerned that changing the
> optimization setting inside one source file could cause the
> change to s
Does ASDF set compiler optimization settings before compiling
each file when building? I'm concerned that changing the
optimization setting inside one source file could cause the
change to stick and be used for other files. I don't think the
CL standard mandates that "(declaim (optimize ... ))" a
Tobias C. Rittweiler wrote:
> Robert Goldman writes:
>
>> Fare wrote:
>>
Do we need a :after method to restore the old settings? I'm not sure
how to do that actually, since I don't believe there's a portable way to
record them. Do you have thoughts about this?
>>> (rpg replie
Faré wrote:
> While developing XCVB, I was reminded that when you declaim or
> compile-toplevel proclaim optimization settings, these settings may
> (ccl, allegro) or may not (cmucl, sbcl) persist beyond the compilation
> of the current file. To make the build deterministic, XCVB now resets
> the s
While developing XCVB, I was reminded that when you declaim or
compile-toplevel proclaim optimization settings, these settings may
(ccl, allegro) or may not (cmucl, sbcl) persist beyond the compilation
of the current file. To make the build deterministic, XCVB now resets
the settings before every o
10 matches
Mail list logo
