|
From: | Jörg F . Wittenberger |
Subject: | Re: [Chicken-users] types.db incorrect |
Date: | 08 Sep 2011 13:07:06 +0200 |
On Sep 6 2011, Felix wrote:
Thanks agauin, Joerg. I pushed this change as well.If not, how would I turn the consequence - which is wrong code at this time - into a warning?You can check the results of specialization with "-debug P" (which dumps the program after specialization has taken place). "-debug x" shows the specializations done. You can switch off specialization by just compiling with "-O2". That way you can check whether "-specialize" (enabled by -O3 and higher) results in incorrect code.
Thanks a lot for that one. I better had returned to the list earlier. The past days I spent (and failed so far) trying to locate a problem I never had in the LLRB tree code. At least that's where it comes up. In this context I found that the manual mentions {{-debug ?}} to find a summary of the available debug arguments. However this gave me: chicken -debug '?' Error: missing argument to `-debug' option .....
[Prev in Thread] | Current Thread | [Next in Thread] |