This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: CPython vs libstdc++
- From: Carlos O'Donell <carlos at redhat dot com>
- To: Zack Weinberg <zackw at panix dot com>, GNU C Library <libc-alpha at sourceware dot org>, libstdc++ at gcc dot gnu dot org
- Cc: Sumana Harihareswara <sh at changeset dot nyc>
- Date: Thu, 11 Jul 2019 22:05:56 -0400
- Subject: Re: CPython vs libstdc++
- References: <CAKCAbMjgTPsguEm4TND4M491M72LY-806FhB3CuA7VbCW=je1w@mail.gmail.com>
On 7/11/19 12:13 PM, Zack Weinberg wrote:
I have been investigating a mysterious problem with Python extension
modules that use C++ internally. If I'm right about the cause, I
suspect that it can't be fixed without changes to the dynamic linker,
and I think we may need to have a dialogue between Python core
maintainers and GNU toolchain maintainers to figure out what Python
wants to be possible and how much of that is feasible for GCC and
glibc to support.
I agree completely.
I try to stay integrated into Python (manylinux issues), Ruby (malloc
issues), llvm lld (CET markup), and other toolchain issues and
language issues.
Do you have a bug # or something where we can discuss the issue
upstream with the Python developers in question?
--
Cheers,
Carlos.
P.S.
Makes me think of this:
https://www.slideshare.net/StefanusDuToit/cpp-con-2014-hourglass-interfaces-for-c-apis