[Pnet-developers] [Bug #4014] [0.5.8] Hard limit for bytecode size is different in VM bytecode verifier and ilverify

[nobody]

=================== BUG #4014: FULL BUG SNAPSHOT ===================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4014&group_id=353

Submitted by: yannis_bres             Project: DotGNU Portable.NET          
Submitted on: Wed 06/18/03 at 09:53
Category:  None                       Severity:  5 - Major                  
Bug Group:  None                      Resolution:  None                     
Assigned to:  None                    Status:  Open                         

Summary:  [0.5.8] Hard limit  for bytecode size is different in VM bytecode 
verifier and ilverify

Original Submission:  Hi !
The hard limit for bytecode size seems not to be the same for the VM embedded 
bytecode verifier (ilrun) and the dedicated one (ilverify).
Moreover the limit in the VM is not the same than in Mono or M$ VMs.  
Therefore, we reached a point a which our generated code cannot be run with 
PNet VM although it can be verified by ilverify and run by Mono or M$ VM.
It would be nice to increase this limit, but also to provide a command-line 
option to set it.
If you can provide me hints for such a modification, I could provide a patch.
In the same fashion, the default 8K limit for stack is ridiculous :  we work on 
functional language compilation, and recursion can be quite deep when functions 
are not automatically derecursived.  In a more general way, think of a merge 
sort on a linked list...
Best regards,
     Yannis




No Followups Have Been Posted


CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=4014&group_id=353