[Development] QtV8: Order of arguments on Runtime::kResolvePossiblyDirectEval inconsistent

Holger Hans Peter Freyther holger at freyther.de
Tue May 8 23:04:59 CEST 2012


I am looking into why QtV8 stopped working for MIPS (the obvious candidate is
that there is lithium support now). While doing this I noted that in
FullCodeGenerator::EmitResolvePossiblyDirectEval the following is not consistent:

1.) language_mode
2.) is_qml_mode
3.) start_position

ia32, mips, amd64:
1.) language_mode
2.) start_position
3.) is_qml_mode

the ResolvePossiblyDirectEval is shared across all implementations. So is the
ARM code wrong?

More information about the Development mailing list