This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On 07/09/2010 01:06 AM, Richard Earnshaw wrote: > On 08/07/10 23:47, Bernd Schmidt wrote: >> >> On 07/09/2010 12:46 AM, Richard Earnshaw wrote: >>> You also need a test that the optimization isn't used when the result >>> would be clobbered. For example, if the function returned long long and >>> 12 bytes needed to be popped. >>> >>> OK with that change. >> >> Surely that's covered by all the existing execute test? >> >> >> Bernd >> >> > Such as? I'd expect something in gcc.c-torture/execute or maybe libstdc++ would fail if we clobbered return values. > I'd like to be sure that this is clearly tested. I've added a new execute test. Committed. Bernd
Attachment:
t1-epilogue-final.diff
Description: Text document
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |