This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/78509] [7 regression] ICE in in excess_precision_type, at tree.c:8875
- From: "jakub at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 24 Nov 2016 12:11:40 +0000
- Subject: [Bug target/78509] [7 regression] ICE in in excess_precision_type, at tree.c:8875
- Auto-submitted: auto-generated
- References: <bug-78509-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78509
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to James Greenhalgh from comment #6)
> None of the logic was there in the original code, so there is not much to
> compare.
?? Since -fexcess-precision=standard has been introduced, gcc has the excess
precision notion. So there is something to compare.
E.g. try
float foo (float x, float y, float z)
{
return x + y + z;
}
before your changes with
-fdump-tree-gimple -m32 -msse2 -mno-80387 -fexcess-precision=standard
-fdump-tree-gimple -m32 -msse2 -mfpmath=387+sse -fexcess-precision=standard
-fdump-tree-gimple -m32 -msse2 -mfpmath=387 -fexcess-precision=standard
-fdump-tree-gimple -m32 -msse2 -mfpmath=sse -fexcess-precision=standard
-fdump-tree-gimple -m32 -msse -mno-sse2 -mfpmath=sse
-fexcess-precision=standard
to match the different cases in your hook, and compare that to what you get
with the current trunk.