Follow-up Comment #8, bug #30766 (project gnustep): >> Base 1.19.3 runs fine, so I guess they can be ruled out right >> away.
> Unfortunately not as it's perfectly possible for some code to > trigger bugs in the compiler or runtime that other code does > not trigger. Right, I was thinking along the same line as well right after I sent the message. Today I got an account on the GCC compile farm (http://gcc.gnu.org/wiki/CompileFarm) and could not reproduce the problem on gcc61.fsffrance.org with Base 1.20.1, compiled with manually built GCC 4.4.4. I'm now building the same version of GCC + Debian-specific patches; if it exposes the problem, I'll pass the hot potato to the Debian GCC maintainers. But we'll still need some workaround to get functional GNUstep on this architecture. > My only new idea on how to proceed is to try a bisection > of the code changes since 1.19.3. Yes, I was going to do exactly this if I was fortunate enough to reproduce. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?30766> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/ _______________________________________________ Bug-gnustep mailing list Bug-gnustep@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnustep
