[PATCH, libstdc++] Update abi-check alpha baseline for 4.4

[Jakub Jelinek]

On Thu, Apr 16, 2009 at 09:16:09AM +0200, Uros Bizjak wrote:
> On Thu, Apr 16, 2009 at 9:04 AM, Uros Bizjak <ubizjak@gmail.com> wrote:
> 
> > This patch updates the alpha baseline symbols.  OK for 4.4 and trunk?
> >
> >        * config/abi/post/alpha-linux-gnu/baseline_symbols.txt: Regenerate.
> 
> Hm, the script generates this rather suspicious change:
> 
> -FUNC:acosl@@GLIBCXX_3.4.3
> -FUNC:asinl@@GLIBCXX_3.4.3
> -FUNC:atan2l@@GLIBCXX_3.4
> -FUNC:atanl@@GLIBCXX_3.4.3
> -FUNC:ceill@@GLIBCXX_3.4.3
> -FUNC:coshl@@GLIBCXX_3.4
> -FUNC:cosl@@GLIBCXX_3.4
> -FUNC:expl@@GLIBCXX_3.4
> -FUNC:floorl@@GLIBCXX_3.4.3
> -FUNC:fmodl@@GLIBCXX_3.4.3
> -FUNC:frexpl@@GLIBCXX_3.4.3
> -FUNC:hypotl@@GLIBCXX_3.4
> -FUNC:ldexpl@@GLIBCXX_3.4.3
> -FUNC:log10l@@GLIBCXX_3.4
> -FUNC:logl@@GLIBCXX_3.4
> -FUNC:modfl@@GLIBCXX_3.4.3
> -FUNC:powl@@GLIBCXX_3.4
> -FUNC:sinhl@@GLIBCXX_3.4
> -FUNC:sinl@@GLIBCXX_3.4
> -FUNC:sqrtl@@GLIBCXX_3.4
> -FUNC:tanhl@@GLIBCXX_3.4
> -FUNC:tanl@@GLIBCXX_3.4
> +FUNC:__once_proxy@@GLIBCXX_3.4.11
> +FUNC:acosl@GLIBCXX_3.4.3
> +FUNC:asinl@GLIBCXX_3.4.3
> +FUNC:atan2l@GLIBCXX_3.4
> +FUNC:atanl@GLIBCXX_3.4.3
> +FUNC:atomic_flag_clear_explicit@@GLIBCXX_3.4.11
> +FUNC:atomic_flag_test_and_set_explicit@@GLIBCXX_3.4.11
> +FUNC:ceill@GLIBCXX_3.4.3
> +FUNC:coshl@GLIBCXX_3.4
> +FUNC:cosl@GLIBCXX_3.4
> +FUNC:expl@GLIBCXX_3.4
> +FUNC:floorl@GLIBCXX_3.4.3
> +FUNC:fmodl@GLIBCXX_3.4.3
> +FUNC:frexpl@GLIBCXX_3.4.3
> +FUNC:hypotl@GLIBCXX_3.4
> +FUNC:ldexpl@GLIBCXX_3.4.3
> +FUNC:log10l@GLIBCXX_3.4
> +FUNC:logl@GLIBCXX_3.4
> +FUNC:modfl@GLIBCXX_3.4.3
> +FUNC:powl@GLIBCXX_3.4
> +FUNC:sinhl@GLIBCXX_3.4
> +FUNC:sinl@GLIBCXX_3.4
> +FUNC:sqrtl@GLIBCXX_3.4
> +FUNC:tanhl@GLIBCXX_3.4
> +FUNC:tanl@GLIBCXX_3.4
> 
> Note only one "@" in the new generated symbols. Is this OK?

Yes, a @@ -> @ change is ok, if the symbol name and symbol version are
otherwise the same.
@@ -> @ changes happen either if the same symbol name gets a newer default
symbol version (usually not the case in libstdc++-v3) or when we want to
prevent all new linking from picking up an obsolete symbol, but still
allow already linked shared libraries/binaries to use the symbol (that's the
case of the *l long double math functions here).

	Jakub