https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120955
--- Comment #34 from fiesh at zefix dot tv --- (In reply to Georg-Johann Lay from comment #33) > avr.cc::avr_use_by_pieces_infrastructure_p() is should be. Thank you very much, that's precisely what I was looking for. Now this function depends on the value of MOVE_MAX_PIECES, which used to be 4 and now is 2. (There was no MOVE_RATIO though, and now there is and I suppose it kicks in for optimized builds and makes the load/store instructions be used through tree-inline.cc?) Setting MAX_SIZE to 3 does indeed reduce my data size also for Os to the same level as with O2. https://godbolt.org/z/sscznsrvq appears to indicate for 3 and 4, it's better to do move by pieces for this case?
