Auto byte to int Promotion Bug: use of "0xff", where "0x0ff" is needed

X86BinaryAssembler.java (and potentially others) have code like this:

502	    public final int get32(int offset) {
503	        int v1 = m_data[offset++];
504	        int v2 = m_data[offset++];
505	        int v3 = m_data[offset++];
506	        int v4 = m_data[offset];
507	        return (v1 & 0xFF) | ((v2 & 0xFF) <<  | ((v3 & 0xFF) << 16)
508	            | ((v4 & 0xFF) << 24);
509	    }
510	
511	    public final long get64(int offset) {
512	        long v1 = m_data[offset++];
513	        long v2 = m_data[offset++];
514	        long v3 = m_data[offset++];
515	        long v4 = m_data[offset++];
516	        long v5 = m_data[offset++];
517	        long v6 = m_data[offset++];
518	        long v7 = m_data[offset++];
519	        long v8 = m_data[offset];
520	        return (v1 & 0xFF) | ((v2 & 0xFF) <<  | ((v3 & 0xFF) << 16)
521	            | ((v4 & 0xFF) << 24) | ((v5 & 0xFF) << 32)
522	            | ((v6 & 0xFF) << 40) | ((v7 & 0xFF) << 48)
523	            | ((v8 & 0xFF) << 56);
524	    }
525	
526	    public final int get8(int offset) {
527	        return (m_data[offset] & 0xFF);
528	    }

X86BinaryAssembler.java (and potentially others) SHOULD have code like this:

502	    public final int get32(int offset) {
503	        int v1 = m_data[offset++];
504	        int v2 = m_data[offset++];
505	        int v3 = m_data[offset++];
506	        int v4 = m_data[offset];
507	        return (v1 & 0x0FF) | ((v2 & 0x0FF) <<  | ((v3 & 0x0FF) << 16)
508	            | ((v4 & 0x0FF) << 24);
509	    }
510	
511	    public final long get64(int offset) {
512	        long v1 = m_data[offset++];
513	        long v2 = m_data[offset++];
514	        long v3 = m_data[offset++];
515	        long v4 = m_data[offset++];
516	        long v5 = m_data[offset++];
517	        long v6 = m_data[offset++];
518	        long v7 = m_data[offset++];
519	        long v8 = m_data[offset];
520	        return (v1 & 0x0FFL) | ((v2 & 0x0FFL) <<  | ((v3 & 0x0FFL) << 16)
521	            | ((v4 & 0x0FFL) << 24) | ((v5 & 0x0FFL) << 32)
522	            | ((v6 & 0x0FFL) << 40) | ((v7 & 0x0FFL) << 48)
523	            | ((v8 & 0x0FFL) << 56);
524	    }
525	
526	    public final int get8(int offset) {
527	        return (m_data[offset] & 0x0FF);
528	    }

Where use of "0xFF" should instead be coded as "0x0ff" to avoid AutoInt Promotion bugs.

For example, taking get8(...) method above:
* if m_data[0] is any value 0x080 thru 0x0ff
* then get8(0) will return int value 0x0ffffff80 thru 0x0ffffffff, respectively.

The extra MSB 31 thru 8 are set due to "0xFF" being autopromoted to int value "0x0FFFFFFFF".

I would suggest a gate wide search to avoid further cases of this issue.