[Bug libc/29812] New: Tunables for libstdc++

[Bug libc/29812] New: Tunables for libstdc++

[jwakely.gcc at gmail dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=29812

            Bug ID: 29812
           Summary: Tunables for libstdc++
           Product: glibc
           Version: unspecified
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: jwakely.gcc at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

There are several things I'd like to use tunables for in libstdc++:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88264

But there's no thread-safe way to do that if libstdc++.so can be dlopened.

Would it be possible for glibc to reserve some tunables under the glibcxx.*
namespace and provide a safe way for libstdc++ to get read-only access to
those?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug libc/29812] Tunables for libstdc++

[adhemerval.zanella at linaro dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=29812

Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adhemerval.zanella at linaro dot o
                   |                            |rg

--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
The main issue about reserving names for libstdc++ and other projects is that
once we do it would become a stable API, which is not the intention for this
feature (we explicitly state it in the documentation).

What might be feasible would be to save all other namespaces tuples and provide
an API to read them, it would be up to consumers to validate the data. I am not
sure yet about the security implications if any.

-- 
You are receiving this mail because:
You are on the CC list for the bug.