libmudflap.cth/pass39-frag.c (and I think pass37-frag.c) produce mudflap violations on Alpha. In dmesg, you get messages like these: pass39-frag.exe(7421): unaligned trap at 0000000120001ff8: b029001c2022000f 29 1 pass39-frag.exe(7552): unaligned trap at 0000000120001ff8: b029001c2022000f 29 1 pass39-frag.exe(7421): unaligned trap at 0000000120001ff8: b029001c2022000f 29 1 I'll attach the relevant portions of libmudflap.log.
Created attachment 11691 [details] testsuite logs
It looks like only the statically linked multithreding test cases trigger the problem. Would you mind trying ot hand-build one of those executables, but adding -rdynamic to LDFLAGS, and run with -backtrace=99 in MUDFLAP_OPTIONS? That way, the backtraces should have more symbolic information.
Created attachment 11705 [details] more detailed log This is with the options you specified but it seems it doesn't contain so much more information. Did I do something wrong or is that what you were looking for?
Closing 4.1 branch.
This does not fail on 4.4 [1] branch. [1] http://gcc.gnu.org/ml/gcc-testresults/2008-12/msg01564.html
Can someone check if this still fails on latest 4.3 branch? 4.4 works OK.
Closing 4.2 branch.
GCC 4.3.4 is being released, adjusting target milestone.
(In reply to comment #6) > Can someone check if this still fails on latest 4.3 branch? It doesn't. See [1]. [1] http://gcc.gnu.org/ml/gcc-testresults/2009-09/msg01497.html