headers
Rémy | 1 Nov 2010 15:42
Picon
Favicon

Disabling the automated code deletion when compiling.

Greetings,

I hope I'm posting at the right place: so, here is my problem. I recently had to 
adapt an old piece of software to the latest version of CMU-CL. While it worked 
perfectly fine with the 18c release, bugs appeared when I used the 19b and, 
finally, entire features are missing when compiled with the 20b version. 
According to the compilation logs, it seems the problems are caused by the 
automated deletion of code, in my opinion because of subtle type errors in the 
source code. Nevertheless, because of the size of the project, and its 
priorities, we cannot work on these corrections. 

Hence I would like to know if there was a possibility to disable the code 
deletion feature during compilation, so as to test this hypothesis? I tried an 
(optimize (safety 0)) , but it did not change the "missing" parts of the code.

Thank you for your help,

Remy Chretien

      
_______________________________________________
cmucl-help mailing list
cmucl-help <at> cmucl.cons.org
http://lists.zs64.net/mailman/listinfo/cmucl-help
Permalink | Reply |
headers
Raymond Toy | 2 Nov 2010 17:04
Picon

Re: Disabling the automated code deletion when compiling.

On 11/1/10 10:42 AM, Rémy wrote:
> Greetings,
>
> I hope I'm posting at the right place: so, here is my problem. I recently had to 
> adapt an old piece of software to the latest version of CMU-CL. While it worked 
> perfectly fine with the 18c release, bugs appeared when I used the 19b and, 
> finally, entire features are missing when compiled with the 20b version. 
> According to the compilation logs, it seems the problems are caused by the 
> automated deletion of code, in my opinion because of subtle type errors in the 
> source code. Nevertheless, because of the size of the project, and its 
> priorities, we cannot work on these corrections. 
>
Can you provide some snippets from the compilation logs?  That would
help understand what the issue is.  Even better would be the actual code
that shows the problem.
> Hence I would like to know if there was a possibility to disable the code 
> deletion feature during compilation, so as to test this hypothesis? I tried an 
> (optimize (safety 0)) , but it did not change the "missing" parts of the code.
I'll have to dig through the compiler to see if it's possible to turn
this off.

Ray

_______________________________________________
cmucl-help mailing list
cmucl-help <at> cmucl.cons.org
http://lists.zs64.net/mailman/listinfo/cmucl-help
Permalink | Reply |

Gmane