-
Notifications
You must be signed in to change notification settings - Fork 19
case_limit #5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It is limited to 64, because that is what the original Spin compiler is limited to. |
It may be useful in the long run to introduce an option which explicitly removes certain limits. |
Added a new Unused Method Removal option (-u). This option still needs testing, use with caution. (Issue #9) Increased the pubcon list buffer size to 32K. (issue #14) Fixed a crash bug in the preprocessor. (issue #16) Renamed a few .c files to .cpp. The solution & project files are now VS2013 format. You can get VS2013 community edition free.
Increased case_limit to 256. (issue #5) Added a new Unused Method Removal option (-u). This option still needs testing, use with caution. (Issue #9) Increased the pubcon list buffer size to 32K. (issue #14) Fixed a crash bug in the preprocessor. (issue #16) Renamed a few .c files to .cpp. The solution & project files are now VS2013 format. You can get VS2013 community edition free.
So this means the case limit still applies (64)? Just seemed odd that the limit was increased and then removed again (according to the log messages). |
No, I had submitted a partial set of files, reverted that, and then submitted the full set of files. The partial set of files didn't have a summary description while the full set did, this may have caused your confusion? Just click the ... buttons to see the full description of the submits to see that the 3rd one also has the case_limit change to 256 in it. |
OK. It's Monday morning here before my first coffee. I'll check later. Thanks. |
Can you do something about the build errors (simple make invocation)?
|
It compiles fine under gcc 4.6.2. Since when did they change it so that explicitly casting doesn't get rid of the "loses precision" thing? And when did that become an error instead of a warning? |
I submitted a fixup for you that should work. I don't have gcc 4.8.3 available right now to test on, so if there were other problems besides what you listed then it'll have to wait. It's annoying how they keep changing what is a warning or error and that even with an explicit cast they now don't shut up about lost precision and call it an error. |
Compiles on Debian8 (gcc version 4.9.2). |
For some of my projects I need a higher case_limit (e.g. 256). Is there any reason to set this to 64?
The text was updated successfully, but these errors were encountered: