[Bug target/11787] always call memcpy for block move in mips16

2007-11-15 Thread rsandifo at gcc dot gnu dot org
--- Comment #6 from rsandifo at gcc dot gnu dot org 2007-11-15 20:52 --- Fixed on mainline, and not appropriate for backporting. -- rsandifo at gcc dot gnu dot org changed: What|Removed |Added --

[Bug target/11787] always call memcpy for block move in mips16

2007-08-24 Thread sandra at gcc dot gnu dot org
--- Comment #5 from sandra at gcc dot gnu dot org 2007-08-24 23:54 --- Subject: Bug 11787 Author: sandra Date: Fri Aug 24 23:54:05 2007 New Revision: 127790 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=127790 Log: 2007-08-24 Sandra Loosemore <[EMAIL PROTECTED]> N

[Bug target/11787] always call memcpy for block move in mips16

2005-04-06 Thread echristo at redhat dot com
--- Additional Comments From echristo at redhat dot com 2005-04-06 18:57 --- There's also the problem that the current mechanism for doing unaligned loads/stores are not valid mips16 instructions, and therefore we couldn't rely upon the patterns unless we knew that the addresses were ali

[Bug target/11787] always call memcpy for block move in mips16

2005-04-06 Thread stephane dot mutz at philips dot com
--- Additional Comments From stephane dot mutz at philips dot com 2005-04-06 08:07 --- I understand your point. However, this sometimes results in a significant drop of performance forcing to revert to MIPS2 / MIPS32. This partly spoils the usefulness of MIPS16. I think the option of f

[Bug target/11787] always call memcpy for block move in mips16

2005-04-05 Thread echristo at redhat dot com
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |echristo at redhat dot com |dot org | Status|WAITING

[Bug target/11787] always call memcpy for block move in mips16

2005-04-05 Thread echristo at redhat dot com
--- Additional Comments From echristo at redhat dot com 2005-04-05 21:23 --- The point of mips16 is smaller code, why would you expect inline memcpy calls at any point? -eric -- What|Removed |Added