On Tue, Oct 23, 2018 at 07:40:04PM -0400, Michael Meissner wrote: > On Tue, Oct 23, 2018 at 10:22:41PM +0000, Joseph Myers wrote: > > Now, you can't use the __<func>ieee128 names with *current* glibc because > > they aren't exported yet. So is the plan that GCC would later switch to > > using the __<func>ieee128 names when available based on TARGET_GLIBC_MAJOR > > and TARGET_GLIBC_MINOR (as more namespace-correct, and available for some > > functions without <func>f128 variants), with use of <func>f128 only a > > fallback for older glibc versions lacking __<func>ieee128? > > I suspect the timing may not be right for GCC 9, since I tend to use the > Advance Toolchain to get newer glibc's, and they are on 2.28. I just tried > it, > and as you said, they aren't exported yet.
GCC 9 won't be released until half a year from now. Segher
