"Steven W. Scott" <codekraken@???> writes:
> Just curious, anyone else getting segfaults after compiling with gcc -O3
> optimization flag on alpha 4? Same system, same code, same flags work ok on
> Wheezy. If I back down to -O2 no problems.

If the program segfaults reproducibly (or somewhat reproducibly),
getting to the bottom of this shouldn't be overly difficult: Enable
core dumps[*],

ulimit -c <max core size in K>

collect the resulting file, analyze with gdb

gdb <program file> <core file>

At the very least, this will enable locating the faulting instruction
and from there, it should be possible to work out the cause.

[This is probably again 'dangerous' "this cannot seriously be
--- what a disgusting blowhard!" statement, however, I do actually do
this all of the time and this feature has been immensly helpful to me].

 [*] I still suspect that 'distributions' started to disable this by
     default in order to reduce the number of people expecting such bugs
     to be fixed :->.