https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104208
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot
gnu.org
Last reconfirmed| |2022-03-01
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
So the change that is hitting us here was an (overeager?) attempt by me in
PR87496 to catch conflicting options:
+ else if (global_options_set.x_rs6000_ieeequad)
+ {
+ if (global_options.x_rs6000_ieeequad)
+ error ("%qs requires %qs", "-mabi=ieeelongdouble",
"-mlong-double-128");
+ else
+ error ("%qs requires %qs", "-mabi=ibmlongdouble", "-mlong-double-128");
+ }
In talking with the clang developers about this issue, they ignore the
-mabi={ibm,ieee}longdouble option in the presence of -mlong-double-64 like we
used to do, so I think the most convenient solution for everyone is to just
revert the hunk above from my previous patch, which does fix the issue seen in
glibc.
