pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christoph Berg <myon@debian.org>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [patch] Support LLVM 7
Date: Thu, 20 Sep 2018 23:03:15 +0200
Message-ID: <20180920210315.GB21756@msg.df7cb.de> (raw)
In-Reply-To: <20180920173238.f5idtzdlpkjsufv5@alap3.anarazel.de>
References: <20180912124517.GD24584@msg.df7cb.de>
	<20180912210338.h3vsss5lkuu26ua2@alap3.anarazel.de>
	<20180912210734.GB5666@msg.df7cb.de>
	<20180916074833.GB4707@msg.df7cb.de>
	<20180919222600.myk5nec6unhrj45k@alap3.anarazel.de>
	<20180920081044.GA16897@msg.df7cb.de>
	<20180920173238.f5idtzdlpkjsufv5@alap3.anarazel.de>

Re: Andres Freund 2018-09-20 <20180920173238.f5idtzdlpkjsufv5@alap3.anarazel.de>
> That's pretty clearly an LLVM bug. Could you enable jit_dump_bitcode and
> send the bitcode files (I assume there should be something like
> <pid>.<generation>.bc and the same with <prefix>.optimized.bc) from the
> data directory?
> 
> Not that I think x32 is a particularly popular database platform, but
> LLVM clearly needs to be fixed independent of PG...

$ PGOPTIONS="-c jit_debugging_support=on" psql
psql (11beta4 (Debian 11~beta4-2))
postgres=# set jit=on;
postgres=# set jit_dump_bitcode = on;
postgres=# \i /home/cbe/postgresql/debian/11/src/test/regress/sql/boolean.sql 

FATAL:  fatal llvm error: Cannot select: 0x580bfdf0: ch,glue = X86ISD::CALL 0x580bfd60, 0x580bfec8, Register:i32 $edi, RegisterMask:Untyped, 0x580bfd60:1
  0x580bfec8: i32 = X86ISD::Wrapper TargetGlobalAddress:i32<void (%struct.TupleTableSlot*)* @deform_0_1> 0
    0x580bfe80: i32 = TargetGlobalAddress<void (%struct.TupleTableSlot*)* @deform_0_1> 0
  0x580bfd18: i32 = Register $edi
  0x580bfda8: Untyped = RegisterMask
  0x580bfd60: ch,glue = CopyToReg 0x580bfcd0, Register:i32 $edi, 0x580bfc40
    0x580bfd18: i32 = Register $edi
    0x580bfc40: i32,ch = CopyFromReg 0x5807eeec, Register:i32 %27
      0x580bfbf8: i32 = Register %27
In function: evalexpr_0_0
Server beendete die Verbindung unerwartet

gdb reports "exited with code 01" at that point.

Christoph




view thread (14+ messages)  latest in thread

Message-ID: <20180920210315.GB21756@msg.df7cb.de>
Permalink:  ../20180920210315.GB21756@msg.df7cb.de/
Also on:    postgresql.org/message-id/20180920210315.GB21756@msg.df7cb.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: myon@debian.org, andres@anarazel.de
  Subject: Re: [patch] Support LLVM 7
  In-Reply-To: <20180920210315.GB21756@msg.df7cb.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox