From: Tom Lane <tgl@sss.pgh.pa.us>
To: Dmitry Dolgov <9erthalion6@gmail.com>
cc: Michael Paquier <michael.paquier@gmail.com>,
        Vincent Lachenal <vincent.lachenal@gmail.com>,
        PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: BUG #14897: Segfault on statitics SQL request
In-reply-to: 
 <CA+q6zcVE2FQ9irhENEy=2WjRWgV2hyzfYyOXFs36w=hsk4faBw@mail.gmail.com>
References: <20171110185747.31519.28038@wrigleys.postgresql.org>
 <1415.1510340891@sss.pgh.pa.us>
 <CAA2tJ7o-VK+ghsxifDAszFN5fikmG6U3sWHCEvc9nAVOypfjAw@mail.gmail.com>
 <5652.1510344738@sss.pgh.pa.us>
 <CAA2tJ7qsopt0hHbsm397H62LMsaE4hjRwaUu3FQdNgo5AYAGXA@mail.gmail.com>
 <7710.1510346813@sss.pgh.pa.us>
 <CAA2tJ7odG4KB=wvu_+5FfssxckbLTnEuR9C_TXRyeU_35z+CSA@mail.gmail.com>
 <10197.1510349123@sss.pgh.pa.us>
 <CAA2tJ7p72wbuHEzOA_g2V4YcmeDPHYKggenTR4dXG=kSpCiO8Q@mail.gmail.com>
 <14075.1510352167@sss.pgh.pa.us>
 <CA+q6zcXe9aV5NV88u9Y=vMp+=fP7QOXgTyFQhzuvmCvTBvb_kQ@mail.gmail.com>
 <17617.1510355215@sss.pgh.pa.us>
 <CAB7nPqR7mWvtnALZF93oez_v03NFCJ8dXP9CNicaUDv3KjDbYw@mail.gmail.com>
 <CA+q6zcVE2FQ9irhENEy=2WjRWgV2hyzfYyOXFs36w=hsk4faBw@mail.gmail.com>
Comments: In-reply-to Dmitry Dolgov <9erthalion6@gmail.com>
	message dated "Sat, 11 Nov 2017 11:34:09 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <643.1510418216.1@sss.pgh.pa.us>
Date: Sat, 11 Nov 2017 11:36:56 -0500
Message-ID: <644.1510418216@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-bugs-owner@postgresql.org

Dmitry Dolgov <9erthalion6@gmail.com> writes:
>> On 11 November 2017 at 09:39, Michael Paquier <michael.paquier@gmail.com>
> wrote:
>> My laptop uses Arch, and I can see the crash easily when compiling
>> with gcc 7.2 which is the one bundled in the core package set

> Yes, I forgot to mention, that I also used quite recent version of gcc
> (GCC) 8.0.0 20170805 (experimental).

Would you guys who are seeing the problem note whether the address of
the int128 field is 16-aligned, or only 8-aligned?

Also, it'd be real useful to see some disassembly around the point of
the crash, so that we can check whether the compiler is using SIMD
instructions.  (Or just get the compiler to generate a numeric.s file
with -S.)

I'm pretty suspicious that this is where the problem is, but it would
be good to have confirmation before we put effort into a fix.

			regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs