This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH, v3] Potential solution to librt issue.
What does this imply for your idea? I understand, correct me if I'm
wrong, that not-exporting the symbol, arranging for the call to be
inside an header, would make the issue easier to solve. But then, what
would happen if the user code actually uses now? Would have to be linked
on a case-by-case basic to libpthread?
Yes, but we could arrange it so that the libpthread linking occurs
automagically. Note that adding -lpthread is also automatic when you
add -lrt; so Chris' patch is only breaking -static, whereas in the
common case it only affects performance.
Paolo
- References:
- [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.