2 Bug in code emitted by "return" pattern on CRIS: missing pop of
3 forced return address on stack. */
4 /* { dg-require-effective-target return_address } */
7 void *f (int) __attribute__ ((__noinline__
));
11 /* The code does a little brittle song and dance to trig the "return"
12 pattern instead of the function epilogue. This must still be a
13 leaf function for the bug to be exposed. */
16 return __builtin_return_address (0);
23 return __builtin_return_address (0);
30 void *y (int i
) __attribute__ ((__noinline__
,__noclone__
));
36 /* This must not be a sibling call: the return address must appear
37 constant for different calls to this function. Postincrementing x
38 catches otherwise unidentified multiple returns (e.g. through the
39 return-address register and then this epilogue popping the address
40 stored on stack in "f"). */
41 return (char *) f (i
) + x
++;
49 /* Can't reasonably check the validity of the return address
50 above, but it's not that important: the test-case will probably
51 crash on the first call to f with the bug present, or it will
52 run wild including returning early (in y or here), so we also
53 try and check the number of calls. */