blob: c71ec4d34b2b30d4c00d6969d8009c32d33318c7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
/* PR optimization/10392
* Reporter: marcus@mc.pp.se
* Summary: [3.3/3.4 regression] [SH] optimizer generates faulty array indexing
* Description:
* The address calculation of an index operation on an array on the stack
* can _under some conditions_ get messed up completely
*
* Testcase tweaked by dank@kegel.com
* Problem only happens with -O2 -m4, so it should only happen on sh4,
* but what the heck, let's test other architectures, too.
* Not marked as xfail since it's a regression.
*/
/* { dg-do run } */
/* { dg-options "-O2" } */
/* { dg-options "-O2 -m4" { target sh4-*-* } } */
const char *dont_optimize_function_away;
const char *use(const char *str)
{
dont_optimize_function_away = str;
if (str[0] != 'v')
abort();
if (str[1] < '1' || str[1] > '6')
abort();
if (str[2])
abort();
return str[2] ? "notused" : "v6";
}
const char *func(char *a, char *b)
{
char buf[128];
unsigned char i;
const char *result;
char *item[] = {
"v1",
"v2",
};
buf[0] = 'v';
buf[1] = '3';
buf[2] = 0;
for (i = 0; i < 2; i++) {
/* bug is: following line passes wild pointer to use() on sh4 -O2 */
result = use(item[i]);
use(buf);
use(a);
use(b);
result = use(result);
}
return result;
}
int main()
{
func("v4", "v5");
return 0;
}
|
