On Thu, 8 May 2025 at 20:56, Jason Merrill <[email protected]> wrote:
>
> Tested x86_64-pc-linux-gnu. Does this make sense for trunk?
Yes, it looks useful. I'm going to test it with my "very -std and -m32
and old-string ABI" test settings to be sure it doesn't cause any
problems.
> -- 8< --
>
> I added this locally to check whether the PR120012 fix affects libstdc++ (it
> doesn't) but it seems generally useful to catch whether compiler ABI
> changes have library impact.
>
> libstdc++-v3/ChangeLog:
>
> * testsuite/lib/libstdc++.exp: Add -Wabi.
> ---
> libstdc++-v3/testsuite/lib/libstdc++.exp | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libstdc++-v3/testsuite/lib/libstdc++.exp
> b/libstdc++-v3/testsuite/lib/libstdc++.exp
> index 5e958d159de..74e7e5e98eb 100644
> --- a/libstdc++-v3/testsuite/lib/libstdc++.exp
> +++ b/libstdc++-v3/testsuite/lib/libstdc++.exp
> @@ -586,6 +586,7 @@ proc v3_target_compile { source dest type options } {
> global tool
>
> lappend options "additional_flags=-fdiagnostics-plain-output"
> + lappend options "additional_flags=-Wabi=20";
>
> if { [target_info needs_status_wrapper] != "" && [info exists gluefile]
> } {
> lappend options "libs=${gluefile}"
>
> base-commit: abab79397ef97acf7c689c43e27d58d8d7d5c599
> --
> 2.49.0
>
