jaotc fails to build the object file for the given class.
Tianxiao Gu
tianxiao.gu at gmail.com
Mon Jan 22 18:19:36 UTC 2018
@Ben and Andrew and Mark,
Thanks very much for your reply and help! Next time I will update the class
file to github.
Actually, all these StackOverFlow and OutOfMemory issues have been fixed in
the latest JDK 10. So they are not issues anymore. I am sorry for asking
for help without checking that.
Besides, I also found something like
org.graalvm.compiler.graph.GraalGraphError:
org.graalvm.compiler.debug.GraalError:
NormalizeCompareNode connected to org.graalvm.compiler.nodes.
calc.IntegerBelowNode$BelowOp at 6de2ac50 (int[16777215|0xffffff]
17|NormalizeCompare false)
But all these error messages seem to be caused by invalid bytecode
sequences. I wil try to dig it out first.
On Mon, Jan 22, 2018 at 10:11 AM, <mark.reinhold at oracle.com> wrote:
> 2018/1/22 10:00:20 -0800, benjamin.john.evans at gmail.com:
> > The jdk9-dev list strips attachments - so you will need to host the
> > class elsewhere.
>
> The jdk9-dev list, like most OpenJDK mailing lists, retains attachments
> of the following content types:
>
> multipart/mixed
> multipart/alternative
> text/plain
> text/x-diff
> text/x-patch
> message/rfc822
> multipart/signed
>
> So if you want to attach a `.java` source file, just attach it as
> text/plain.
>
> > It's probably easiest to set up a Github or other simple OSS project
> > and put your random class generator, and any examples of classes that
> > fail AOTC there, and then just give the link in your mail.
>
> For IP clarity, many OpenJDK contributors will never follow such a link.
> Material contributions (bug reports, patches, documentation, etc.) must
> come in via OpenJDK infrastructure.
>
> - Mark
>
More information about the jdk9-dev
mailing list