On Thu, 12 Jun 2014 10:50:29, Eric Botcazou wrote: > >> Btw I am not sure at all, why argp-references can never be dangerous? >> For instance in a struct with an array inside, passed as function argument? > > IMO there cannot be any definitive solution to this issue until after we move > all the affected optimizations from RTL to GIMPLE. In the meantime, the > failure mode is not catastrophic (100% reproducible segfault) and there is > always an easy workaround (generally a -fno-* switch). > > -- > Eric Botcazou
not really 100% reproducable. As a little surprise, the test case from the tracker did _not_ crash when I initially put it in the testsuite. Reason, probably, the stack layout in the test suite is a little different, because the LD_LIBRARY_PATH environment variable is sooo long, and all environment variables, and arguments are at the top of the stack. The test did only produce the crash as expected when I changed this if (b == 2837) a = e[b]; into that: if (b == 28378) a = e[b]; Bernd.