search for: r169783

...ls (and segfaults) consistently with an environment (gcc + os) conveniently preserved in a virtual machine. I will confirm that it is gone there and report. Thanks for the fix :) Carlos 2012/12/10 Anshuman Dasgupta <adasgupt at codeaurora.org> > Carlos, > > I committed a fix in r169783. Thanks for catching this. > > However, I could not reproduce an invalid read or a segfault even with > fadd.ll. Is there a test case you can check in that reproduces this bug? > Even if the segfault occurs intermittently, that's better than no test case > at all. > > Thank...

Hi again, I can confirm r169783 fixes the problem. My testbench segfaulted in r169782 but works after your commit. We can close the issue. Thanks, Carlos 2012/12/11 Carlos Sánchez de La Lama <csanchezdll at gmail.com> > Hi Anshu, > > I got a testbench which fails (and segfaults) consistently with an > envi...

...you please check in that test case or better still, a reduced version of that test. Thanks -Anshu --- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation On 12/11/2012 5:47 AM, Carlos Sánchez de La Lama wrote: > Hi again, > > I can confirm r169783 fixes the problem. My testbench segfaulted in > r169782 but works after your commit. > > We can close the issue. > > Thanks, > > Carlos > > > 2012/12/11 Carlos Sánchez de La Lama <csanchezdll at gmail.com > <mailto:csanchezdll at gmail.com>> > >...

...educed > version of that test. > > > Thanks > -Anshu > > --- > Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted > by The Linux Foundation > > On 12/11/2012 5:47 AM, Carlos Sánchez de La Lama wrote: > > Hi again, > > I can confirm r169783 fixes the problem. My testbench segfaulted in > r169782 but works after your commit. > > We can close the issue. > > Thanks, > > Carlos > > > 2012/12/11 Carlos Sánchez de La Lama <csanchezdll at gmail.com> > >> Hi Anshu, >> >> I got a testbe...

Carlos, I committed a fix in r169783. Thanks for catching this. However, I could not reproduce an invalid read or a segfault even with fadd.ll. Is there a test case you can check in that reproduces this bug? Even if the segfault occurs intermittently, that's better than no test case at all. Thanks -Anshu --- Qualcomm Innovat...

Hi Anshu, no, I did not fill a bug report. It is not so easy to make the code fail noticeably; during Hexagon CodeGen tests it happens silently and tests pass. I am working on another VLIW backend which uses DFAPacketizer and compiling llvm with gcc-4.4 makes it segfault, but with gcc-4.7 the bug gets hidden again (it still happens, but values after DFAStateEntryTable in memory are such that