Date: Thu, 27 Jun 2013 17:04:28 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Dimitry Andric <dim@FreeBSD.org> Cc: "freebsd-ports@freebsd.org Ports" <freebsd-ports@freebsd.org>, Brooks Davis <brooks@FreeBSD.org>, David Chisnall <theraven@freebsd.org>, Matthias Andree <mandree@FreeBSD.org>, Michael Gmelin <freebsd@grem.de> Subject: Re: Global destructor order problems Message-ID: <20130627140428.GI91021@kib.kiev.ua> In-Reply-To: <51CC411C.4060105@FreeBSD.org> References: <20130626133149.4835f14a@bsd64.grem.de> <7CD9075C-F8D6-41C1-8D21-8B10DF866ECE@FreeBSD.org> <20130626204521.GU91021@kib.kiev.ua> <6900C006-2A57-4EAF-B19A-629A85CBA001@FreeBSD.org> <20130626210534.GY91021@kib.kiev.ua> <A60BFADA-E358-4363-8BED-E154AB327C6B@FreeBSD.org> <20130626231741.497f7a9b@bsd64.grem.de> <20130626212833.GB91021@kib.kiev.ua> <20130627015602.7a437aad@bsd64.grem.de> <51CC411C.4060105@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--OHOABd/r1N6D/+xo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 27, 2013 at 03:41:48PM +0200, Dimitry Andric wrote: > On 2013-06-27 01:56, Michael Gmelin wrote: > > On Thu, 27 Jun 2013 00:28:33 +0300 > > Konstantin Belousov <kostikbel@gmail.com> wrote: > > > >> On Wed, Jun 26, 2013 at 11:17:41PM +0200, Michael Gmelin wrote: > >>> Are you both on the same architecture? > >> > >> I tested both on amd64 and i386. For i386, it was -m32 for clang, and > >> native 32bit gcc 4.8.1, stock build from the tarball. > >> > > > > For completeness sake I tested once more using various compilers > > including gcc 4.8.1 on 10-CURRENT amd64 (see below). >=20 > I have now tested the lang/gcc44, 46, 47, 48 and 49 ports, on both i386 > and amd64. All result in the incorrect destructor order. My build of gcc is stock, not from the ports. Another detail, I built the compiler on stable/9, but use it on both stable and current. I am very curious what makes the my build to generate the code which uses PLT instead of direct reference, but have no time to investigate. I think that we could revert the termination calls to the functions =66rom the dso being unloaded, but this is quite unfortunate, since it will restore the endless series of 'segfault at the process termination' reports. --OHOABd/r1N6D/+xo Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (FreeBSD) iQIcBAEBAgAGBQJRzEZrAAoJEJDCuSvBvK1BRzsP/34vWkdhOfnjvkcANTyKpuZx a5RP05npxVnNgx/1m131IlBvvltmjVitRan6GrDsNi3qTniMbUWCD4dOmHSq/Dul c5YXcXvJ6PiHnKRLRjm5AfvbbCjI2AE10xxLUpCdm6GY/xw6HLOLANQADwjtd4Km /StBg1YizfWZEr2N9IkC4Ynxcjoy0B4wd/a2NnFrqwR8+LwkpuzbF18p/ecYPWs1 MGI+fhbd4ulOLCxzn4eoltaDY8m7/7KkqQgi4QXF+BveG9AqiQBqQYyW0oZ87XhN 8ClPe/JCrSk4AyvFgcjBRMT2wGvvdg83ta/5l+5237o8EFk/vez+Zx6ETR9dL2Qm t7KBSDuRQXOtfghU+b4YWYSjOmsTFthDo+Z8qm9hA82NMFbwboiUMxfvDvb5LIMC CjERJT7nw/F+FXUBmGain2gBWg+EHqlDrSYbHnfIodQq1UesAf2JAM80+mZTZX3p Mw/atNTKb9g07FSB7gMIaaEBvlbR8+8of2dc6M36sp657EncS9P9QUoUnRdvdGUr 4c5Ac75w9txBlWA75tN6HRZZ2ZTX6m4Eme+A3iK44ZVbVDJ3Ok3UP+7ZUcWqKvbw 3DC/W13ntCwHj812g26VtM7fNBFyGxa6xhU4bha1oQk7nmoOf+IodP2LeI0IQ4jn 2ClgV0atCOjMJqo936Mx =iSDB -----END PGP SIGNATURE----- --OHOABd/r1N6D/+xo--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130627140428.GI91021>