- About Scala
- Documentation
- Code Examples
- Software
- Scala Developers
optimise & continuations
Sun, 2010-04-04, 00:58
Two questions:
Do we have some automated process testing under -optimise? I could swear
we did, but now I don't see one in hudson.
And, I find test.continuations.suite very crashy under -optimise. It
also seems to be going for the debugging output world record, I think
there must be a loop in TextPrinter. I'm not overly worried about the
intersection of continuations and -optimise, but for optimise in general
we'd better keep our heel firmly pressed upon him.
Sun, 2010-04-04, 14:07
#2
Re: optimise & continuations
I was assuming that hudson would run all tests with -optimize and I'm surprised to learn it doesn't.
The crashes in test.continuations.suite seem to be due to an optimizer bug:
https://lampsvn.epfl.ch/trac/scala/ticket/3252
I'll try to come up with workaround though.
- Tiark
On Apr 4, 2010, at 1:58 AM, Paul Phillips wrote:
> Two questions:
>
> Do we have some automated process testing under -optimise? I could swear
> we did, but now I don't see one in hudson.
>
> And, I find test.continuations.suite very crashy under -optimise. It
> also seems to be going for the debugging output world record, I think
> there must be a loop in TextPrinter. I'm not overly worried about the
> intersection of continuations and -optimise, but for optimise in general
> we'd better keep our heel firmly pressed upon him.
>
>>>>> "Paul" == Paul Phillips writes:
Paul> And, I find test.continuations.suite very crashy under -optimise.
Paul> It also seems to be going for the debugging output world record,
Paul> I think there must be a loop in TextPrinter.
See for example http://lampsvn.epfl.ch/trac/scala/ticket/3248 . (Reams
of output from TextPrinter. Optimisation on, continuations not
involved.)