On Thu, Feb 17, 2011 at 8:28 PM, Matt Turner wrote: > On Thu, Feb 17, 2011 at 7:15 PM, Guy Martin wrote: >> I've attached a reduced test case. The program is supposed to >> segfault because of a stack overflow. However, with 4.5, it just hangs. >> It seems that 4.5 simply over-optimize the function and replaces it >> with a single jump. > > http://bugs.gentoo.org/show_bug.cgi?id=340923 > > It's known and fixed. It's not a gcc regression, nor is it > HPPA-specific (didn't you try to confirm that it was HPPA-specific? :) > > The reason you're hitting it is that you've keyworded gcc-4.5.2, but > aren't running a full ~hppa system. vapier doesn't seem to acknowledge > that this is a reasonable, sensible, or even common configuration. that's because it is not. there's a difference between running brand new bleeding edge versions of the toolchain on a stable system all the time and running them for the stabilization process. inevitably every gcc/glibc/kernel header upgrade in ~arch breaks a shit ton of stable packages (and even unstable packages), the vast majority of which will be fixed by those packages stabilizing a new version as natural progression by the time the toolchain versions have settled for stabilization. -mike -- 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
