------- Comment #28 from hutchinsonandy at aim dot com 2008-02-02 15:44 -------
The patch and suggestions on this are valid. However, memory moves -
particular with base pointers, may require additional instruction to be added
to reach required displacments. Splitting such moves may well incur the
overhead per BYTE!
So we need to get the pointers sorted so that (for example) 4 separate QI bytes
is just as good as 1 access to 4 SI bytes.
As for other pattern removal YES!
The reason to change MOVE_MAX is not made clear. I understood this to control
the threshold for using movmem rather than inline RTL. movmem wins (in size) at
about 8+ bytes. Does it have another use related to this problem?
--
hutchinsonandy at aim dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hutchinsonandy at aim dot
| |com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11180
