> Could you do the very same test with -fno-delayed-branch ? > > Compiling without that optimization on my system makes the problem go > away. It is really a problem with that part of the code and delayed > branching. That's useful information as it narrows the problem considerably. The problem might be in the PA backend delay slot handling for PA 2.0 32-bit calls, or it might be a reorg problem. The latter are very tricky. > This has been tested with different versions of gcc (4.1.2, 4.2.4, > 4.3.1). Both 4.2 and 4.3 exhibit the issue once you compile with > -march=2.0 and -fdelayed-branch. > > Also, compiling with -march=2.0 -O0 -fdelayed-branch doesn't produce a > segv but produces the following error message : > hope tests # ../src/lzma/lzma -c < in > out > ../src/lzma/lzma: SetCoderProperties() error > > There is really a compiler issue here. We need to find by debugging an example of code that is miscompiled. > Also, not sure if you noticed but values printed in the gdb backtrace > are completely wrong. But that is a different issue as binaries > generated with any compilers shows the same thing. Yes, it's a major problem for debugging and it has gotten worse with each new GCC versions. There have been some discussions on the list about how to improve debugging information. Dave -- J. David Anglin dave.anglin@xxxxxxxxxxxxxx National Research Council of Canada (613) 990-0752 (FAX: 952-6602) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
