http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56897
--- Comment #7 from Uros Bizjak <ubizjak at gmail dot com> 2013-04-16 15:15:14 UTC --- (In reply to comment #4) > Hi, > > (In reply to comment #3) > > Please create a self-sufficient executable testcase, following the > > instructions > > at [1]. I was not able to confirm the problem from the lines you posted. > > Thanks for the feedback, Uros. Did you try it together with the frame > growing downwards diff posted in #56898? If so, the locals are actually > at the negative offsets and unaligned loads like foo%8-5 will expose this, > instead of foo%8-1. No, I am using unpatched compiler. Compiling your ab-pre.tgz test, I got: ~/gcc-build-47/gcc/xgcc -B ~/gcc-build-47/gcc -O a.c uros@monolith ~/test $ ./a.out 0d0a 0d0a0401 0d0a0401 ~/gcc-build-47/gcc/xgcc -B ~/gcc-build-47/gcc -O -mcpu=ev4 a.c uros@monolith ~/test $ ./a.out 0d0a 0d0a0401 0d0a0401 with: GNU C (GCC) version 4.7.3 20130228 (prerelease) [gcc-4_7-branch revision 196343] (alphaev68-unknown-linux-gnu) and the same result (with the same flags) with: GNU C (GCC) version 4.9.0 20130407 (experimental) [trunk revision 197551] (alphaev68-unknown-linux-gnu) The compilers imply -mcpu=ev67 when invoked without -mcpu command.
