Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Handle Unable to pack method, jump in aspectj

Thanks Frank for the update,
//The byte code instructions are defined by the JVM specifications, it's not something AspectJ can change. See http://en.wikipedia.org/wiki/Java_bytecode_instruction_listings.
The given specification is for 32bit jvm or 64bit jvm, If any change exists in 64 bit jvm. Let me know.

Thanks,
Krishna



From: Frank Pavageau <frank.pavageau@xxxxxxxxx>
To: aspectj-users@xxxxxxxxxxx
Date: 09/13/2013 02:08 PM
Subject: Re: [aspectj-users] Handle Unable to pack method, jump in aspectj
Sent by: aspectj-users-bounces@xxxxxxxxxxx





2013/9/13 Krishna Jasty <krishna.jasty@xxxxxxx>
I will work on the method, which is bigger in size and causing this error. I can try to split the single big method into several small pieces.
Meanwhile these exceptions are very common in my application though the aspectj instrumentation is very small.


Big methods are bad anyway : they're hard to read and understand for humans, and might not be compiled by the JIT compiler, in which case they'll run slower than if they had been split into (logical) pieces.
 
 In aspectj source code, where the details of 2 bytes for IFLE and 4 bytes for GOTO is specified.
 How to wider from the initial 2 bytes to 4 bytes. Can i try any alternative in aspectj front to avoid this error.

 
The bytecode instructions are defined by the JVM specifications, it's not something AspectJ can change. See http://en.wikipedia.org/wiki/Java_bytecode_instruction_listings.

Frank_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aspectj-users


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you


Back to the top