Thanks for the explanation. I suspected something like that (interestingly when
I tried disabling all options on my Mac it worked fine…).
I’ll dig some more and let you know.
On 25.11.2013, at 18:42, Eliot Miranda eliot.mira...@gmail.com wrote:
On Mon, Nov 25, 2013 at 9:37 AM, Sven Van
2013/11/26 Max Leske maxle...@gmail.com
Thanks for the explanation. I suspected something like that (interestingly
when I tried disabling all options on my Mac it worked fine…).
This is because you didn't execute: 'OpalCompiler recompileAll'.
I’ll dig some more and let you know.
We
On 26 Nov 2013, at 15:56, Clément Bera bera.clem...@gmail.com wrote:
2013/11/26 Max Leske maxle...@gmail.com
Thanks for the explanation. I suspected something like that (interestingly
when I tried disabling all options on my Mac it worked fine…).
This is because you didn't execute:
On 25 Nov 2013, at 16:26, Max Leske maxle...@gmail.com wrote:
Thanks Clément, that seems to be it. Disabling the timesRepeat inlining makes
most of the builds run through but not all of them. It seems like there’s
another (Opal related?) problem (with the exact same symptoms…).
I’ve
Yeah you cannot compile without inlining specific messages. You can disable
inlining of #timesRepeat: at image level because we added it for fun to see
if it was easy to do in Opal. Now all other optimizations were in the old
compiler and are mandatories. However, you can now in Opal disable these
On 25 Nov 2013, at 17:56, Clément Bera bera.clem...@gmail.com wrote:
Yeah you cannot compile without inlining specific messages. You can disable
inlining of #timesRepeat: at image level because we added it for fun to see
if it was easy to do in Opal. Now all other optimizations were in the
On Mon, Nov 25, 2013 at 9:37 AM, Sven Van Caekenberghe s...@stfx.eu wrote:
On 25 Nov 2013, at 17:56, Clément Bera bera.clem...@gmail.com wrote:
Yeah you cannot compile without inlining specific messages. You can
disable inlining of #timesRepeat: at image level because we added it for
fun
