Andres Freund via llvm-dev
2018-Sep-21 23:54 UTC
[llvm-dev] X32 bugs around "cannot select" lingering around
Hi, There's several, to my eyes, somewhat related looking bugs: Bug 36743 - Cannot select: X86ISD::CALL ICE with -mx32 -O2 -fno-plt https://bugs.llvm.org/show_bug.cgi?id=36743 Bug 34268 - JITting of x32 code on x64 fails with crash or instruction selection error. https://bugs.llvm.org/show_bug.cgi?id=34268 There's unfortunately been no investigation. I'm asking because I hit something eerily looking like the second case, in postgresql. The debian packagers report that postgres' tests fail on x32 when llvm support is enabled. The relevant bitcode excerpt and error is: https://gist.github.com/anarazel/f8fe66e149740479ec8501683008620e Is x32 support considered stable? Greetings, Andres Freund
Chupin, Pavel V via llvm-dev
2018-Sep-25 02:50 UTC
[llvm-dev] X32 bugs around "cannot select" lingering around
I don't think it's stable, unless somebody recently contributed to x32. The last patch I sent was ~4 years ago and there've been quite a few issues left to fix for x32. :(( -- Pavel -----Original Message----- From: Andres Freund [mailto:andres at anarazel.de] Sent: Friday, September 21, 2018 4:55 PM To: llvm-dev <llvm-dev at lists.llvm.org>; Zinovy Nis <zinovy.nis at gmail.com>; Chupin, Pavel V <pavel.v.chupin at intel.com>; Lang Hames <lhames at gmail.com> Subject: X32 bugs around "cannot select" lingering around Hi, There's several, to my eyes, somewhat related looking bugs: Bug 36743 - Cannot select: X86ISD::CALL ICE with -mx32 -O2 -fno-plt https://bugs.llvm.org/show_bug.cgi?id=36743 Bug 34268 - JITting of x32 code on x64 fails with crash or instruction selection error. https://bugs.llvm.org/show_bug.cgi?id=34268 There's unfortunately been no investigation. I'm asking because I hit something eerily looking like the second case, in postgresql. The debian packagers report that postgres' tests fail on x32 when llvm support is enabled. The relevant bitcode excerpt and error is: https://gist.github.com/anarazel/f8fe66e149740479ec8501683008620e Is x32 support considered stable? Greetings, Andres Freund
Derek Schuff via llvm-dev
2018-Sep-25 19:42 UTC
[llvm-dev] X32 bugs around "cannot select" lingering around
As far as I know, nobody is actively maintaining it. Pavel and I have contributed in the past, but neither of us much recently. I occasionally get sent patches and I do review and commit them, but I'm not working on fixing bugs myself. On Mon, Sep 24, 2018 at 9:22 PM Chupin, Pavel V via llvm-dev < llvm-dev at lists.llvm.org> wrote:> I don't think it's stable, unless somebody recently contributed to x32. > The last patch I sent was ~4 years ago and there've been quite a few > issues left to fix for x32. :(( > > -- Pavel > > > -----Original Message----- > From: Andres Freund [mailto:andres at anarazel.de] > Sent: Friday, September 21, 2018 4:55 PM > To: llvm-dev <llvm-dev at lists.llvm.org>; Zinovy Nis <zinovy.nis at gmail.com>; > Chupin, Pavel V <pavel.v.chupin at intel.com>; Lang Hames <lhames at gmail.com> > Subject: X32 bugs around "cannot select" lingering around > > Hi, > > There's several, to my eyes, somewhat related looking bugs: > > Bug 36743 - Cannot select: X86ISD::CALL ICE with -mx32 -O2 -fno-plt > https://bugs.llvm.org/show_bug.cgi?id=36743 > > Bug 34268 - JITting of x32 code on x64 fails with crash or instruction > selection error. > https://bugs.llvm.org/show_bug.cgi?id=34268 > > There's unfortunately been no investigation. > > I'm asking because I hit something eerily looking like the second case, in > postgresql. The debian packagers report that postgres' tests fail on > x32 when llvm support is enabled. The relevant bitcode excerpt and error > is: > > https://gist.github.com/anarazel/f8fe66e149740479ec8501683008620e > > Is x32 support considered stable? > > Greetings, > > Andres Freund > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180925/789cf232/attachment.html>