[Bug java/20104] gij fails on ppc and not on x86

aph at gcc dot gnu dot org gcc-bugzilla@gcc.gnu.org
Tue Feb 22 20:02:00 GMT 2005


------- Additional Comments From aph at gcc dot gnu dot org  2005-02-22 15:05 -------
The failure is here:

package org.eclipse.jdt.internal.compiler.impl;
public class CompilerOptions ...
{
	void updateSeverity(long irritant, Object severityString) {
		if (ERROR.equals(severityString)) {
			this.errorThreshold |= irritant;

and the corresponding bytecode is:

Method name:"updateSeverity" Signature: (long,java.lang.Object)void
Attribute "Code", length:208, max_stack:7, max_locals:4, code_length:110
  0: ldc <String "error">
  2: aload_3
  3: invokevirtual <Method java.lang.String.equals (java.lang.Object)boolean>

The aload_3 looks wrong to me.

So, there are two separate issues:

1.  Why was aload_3 generated?  Which compiler genrated it?

2.  How did this get past the libgcj verifier?

tromey added to CC list to investigate the verifier.

overholt, please let me know how this jar file was generated.

Bug upgraded to critical.


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |critical
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-02-22 15:05:57
               date|                            |


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20104



More information about the Gcc-bugs mailing list