This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH, v3] Potential solution to librt issue.
Paolo Carlini wrote:
Hi,
so, just a small summary of the current "basic" scheme ("basic" in the sense that
> doesn't involve any weakref tricks, system_clock::now moved inline
I am just not sure about this. Some targets, including Windows, do not
support undefined symbols in shared libraries. system_clock::now would
require to be moved inline for those.
We agree on everything else, including the opinion that run-time
failures are bad.
Paolo
- References:
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.
- Re: [PATCH, v3] Potential solution to librt issue.