error: lvalue required as increment operand

	Bottom Previous Topic Next Topic
Register To Post

kas1e

Posted on: 2022/5/2 18:27 #1

Home away from home

@All
Tried to port some old 68k based code from GCC 2.x (strom) and have issues compiling some code, there are full test case:


#define ULONG unsigned int

#define UWORD unsigned short

#define UBYTE unsigned char





int main()

{    

    UBYTE *chunkbuf;

    UBYTE *chunky;

    UBYTE *chunky2; 

    UWORD val;   



    val = *((UWORD*)chunkbuf)++;

    *((UWORD*)chunky2)++ = val;

    *((ULONG*)chunky2)++ = *((ULONG*)chunkbuf)++;

    *((UWORD*)chunky2)++ = *((UWORD*)chunkbuf)++;

}

Don't take into account that things not initialized, etc, i just made a test case to show the errors i got in the "Right" code, with which i need to deal.

Currently i replace things like this:


val = *((UWORD*)chunkbuf)++; 

on

val = (*(UWORD *)&chunkbuf)++; 

 

 

*((UWORD*)chunky2)++ = val; 

on

*(*(UWORD **)&chunky2)++ = val; 

 

 

*((ULONG*)chunky2)++ = *((ULONG*)chunkbuf)++; 

on

*(*(ULONG **)&chunky2)++ = *(*(ULONG **)&chunkbuf)++;

Compiling errors gone, but i not sure if this is correct ones, because i have bugs and crashes.

Can anyone show the correct way of replacing those 4 strings so it will works as expected while compiles on modern gccs ?

Join us to improve dopus5!
AmigaOS4 on youtube

Daytona675x

Re: error: lvalue required as increment operand

Posted on: 2022/5/2 20:01 #2

Not too shy to talk

@kas1e
OMG, delete all you did

For simplicity you could go with a union like this:


union MixedPointer {

  UBYTE *ubyte_ptr;

  UWORD *uword_ptr;

  ULONG *ulong_ptr;

};



int main()

{    

  UBYTE *chunkbuf;

  UBYTE *chunky;

  UBYTE *chunky2; 

  UWORD val;   



  MixedPointer chunky2_mixed;

  MixedPointer chunkbuf_mixed;

        

  chunky2_mixed.ubyte_ptr=chunky2;

  chunkbuf_mixed.ubyte_ptr=chunkbuf;



  val=*chunkbuf_mixed.uword_ptr++;

  *chunky2_mixed.uword_ptr++=val;

  *chunky2_mixed.ulong_ptr++=*chunkbuf_mixed.ulong_ptr++;

  *chunky2_mixed.uword_ptr++=*chunkbuf_mixed.uword_ptr++;

}

Untested TM

[Facebook] [YouTube Channel] [ko-fi]

rjd324

Re: error: lvalue required as increment operand

Posted on: 2022/5/3 8:51 #3

Quite a regular

Just taking the first example of


val=*((UWORD*)chunkbuf)++;

Is the intention just to grab whatever chunkbuf is pointing at and then increment chunkbuf to the next location?


val=*(UWORD*)(chunkbuf++);

This time, the lvalue is chunkbuf. Surely that is what the original intention was...

Not sure if the original intention was to increment the pointer as if it was a UWORD just before getting the value into val.

If liberty means anything at all, it means the right to tell people what they do not want to hear.
George Orwell.

Daytona675x

Re: error: lvalue required as increment operand

Posted on: 2022/5/3 9:26 #4

Not too shy to talk

@rjd324
We cannot be 100% sure what the original purpose was as the code is illegal. Not just because of the casting/++ abuse but also because it guarantees misaligned data accesses which may be a problem depending on the target CPU.

Anyway, apparently the intention is to grab and store chunks of data of different types which are linearly tightly packed into some structure.
And because of lazyness the original coder tried to use the same UBYTE pointers for all different access variants.
It's of course dirty crap. However the old compiler obviously allowed to increase the pointers depending on the type they were casted to, so if it was casted to a temporary UWORD* the ++ operator would increase the original UBYTE* by sizeof(UWORD).

Your


val=*(UWORD*)(chunkbuf++);

has the same semantics as


val=*(UWORD*)(chunkbuf);

++chunkbuf;

and defeats that purpose as it grabs a UWORD but then increases chunkbuf by sizeof(UBYTE) instead of sizeof(UWORD). So the next access would grab parts of the previously read value...
I strongly doubt that this was the original intention.

@kas1e
Of course my union solution doesn't fix potentially misaligned data access.

[Facebook] [YouTube Channel] [ko-fi]

kas1e

Re: error: lvalue required as increment operand

Posted on: 2022/5/3 12:06 #5

Home away from home

@Daniel
Thanks for help as always !

It is some custom FLC player's code. And this is original routine to uncompress chunk into chunky pixels:


void decode_ss2 (UBYTE *chunkbuf, UBYTE *chunky, struct header *h )

{

  UWORD lines, packets, bsize;

  UBYTE *chunky2;

  UWORD val;



  lines = *chunkbuf++;

  lines |= (*chunkbuf++ width - 1) = (packets & 0xff);

        }

    } while (packets >= 32768);



    chunky2 = chunky;

    for ( ; packets > 0; --packets) {

      chunky2 += *chunkbuf++;

      bsize = *chunkbuf++;

      if (bsize > 127)

      {

        bsize = 256 - bsize;

        val = *((UWORD*)chunkbuf)++;



        for ( ; bsize > 0; --bsize)

            *((UWORD*)chunky2)++ = val;

      }

      else

      {

            for( ; bsize > 3; bsize-=4 )

            {

                *((ULONG*)chunky2)++ = *((ULONG*)chunkbuf)++;

                *((ULONG*)chunky2)++ = *((ULONG*)chunkbuf)++;

            }



            for( ; bsize > 0; --bsize )

                *((UWORD*)chunky2)++ = *((UWORD*)chunkbuf)++;

      }

    }

    chunky += s_bpr; // was s_width

  }

}

And decode_ss2 was called as "decode_ss2 (chunkbuf, chunky, &h ); (chunkbuf, chunky, &h ); " in the switch case for FLI_SS2, when we uncompress chunk into chunky pixels.

Edited by kas1e on 2022/5/4 8:14:26

Join us to improve dopus5!
AmigaOS4 on youtube

Register To Post
	Top Previous Topic Next Topic

Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )