https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:b1ed0c9671b99c6b06cbb8c61be14cdec0998de8
commit r13-5751-gb1ed0c9671b99c6b06cbb8c61be14cdec0998de8
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #3 from Jakub Jelinek ---
I mean in mangling...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #2 from Jakub Jelinek ---
Created attachment 54423
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54423=edit
gcc13-pr108698.patch
Actually, if it is just EXCESS_PRECISION_EXPR around REAL_CST, that one can be
handled easily
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108698
--- Comment #1 from Jakub Jelinek ---
Simpler testcase:
template
decltype (T () * T () + 1.0) foo ()
{
return T () * T () + 1.0;
}
void
bar ()
{
foo ();
foo ();
foo ();
}
The question is if the excess precision should be visible
