Hi Kyle,
On 2011/03/26 16:13, Kyle wrote:
I know you all keep the library compiles clean so before creating new warnings
I need some input. I'm planning on issuing warnings when a non-default
optimization is turned on. This would be the following:
* const-detect
* expr-simplify
* load-reduce
* temp-reduce
I don't see what this has to do with the libraries or samples.
Of course to test the libraries we compile, and we want all libraries
and samples to compile without errors or warnings, but that applies to
language-related stuff, not compiler optimizations.
Some samples require -no-variable-reuse to compile in a 'reasonable'
time, some other samples require the opposite because of limited memory.
But otherwise I use default optimization options (don't specify any).
Libraries and samples are Jal files and don't contain compiler options.
Batchfiles, scripts or makefiles may contain compiler options, but these
are not part of the Jallib distribution.
So as far as I can see: no objections against these warnings.
Regards, Rob.
--
R. Hamerling, Netherlands --- http://www.robh.nl
--
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en.
