On Thu, Jul 24, 2014 at 08:55:28PM -0700, Alexei Starovoitov wrote: > > -mno-red-zone only affected prologue emition in gcc. This part didn't > change between the releases. So the bug is quite deep. > What seems to be happening is that 2nd pass of instruction scheduler > (after emit prologue and reg alloc) is ignoring barrier properties > of 'subq $184, %rsp' and moving 'movq $.., -136(%rbp)' instruction > ahead of it. afaik rtl sched was never aware of 'red-zone'. > As an ex-compiler guy, I'm worried that this bug exists in earlier > releases. rtl backend guys need to take a serious look at it. > imo this is very serious bug, since broken red-zone is extremelly > hard to debug.
But wouldn't it be rather trivial to run a static analyzer on the final vmlinux to make sure there are no red zones? I mean, you would only need to read each function and check to make sure that the offset of rbp is within the change of rsp, wouldn't you? Almost seems like an objdump -rd into a perl script could do this. -- Steve > There are two weak test in gcc testsuite related to -mno-red-zone, > but not a single test that actually check that it is doing > the right thing. It is scary. I hope I'm wrong with this analysis. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
