This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/79095] [7 regression] spurious stringop-overflow warning
- From: "glisse at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 22 Jan 2017 10:45:17 +0000
- Subject: [Bug c++/79095] [7 regression] spurious stringop-overflow warning
- Auto-submitted: auto-generated
- References: <bug-79095-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79095
--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> VRP already handles that,
Nice :-) Thanks and sorry for not checking myself.
> IFN_*_OVERFLOW can appear already during gimplification if
> __builtin_*_overflow{,_p} is used in the source.
Yes, I meant that in the original testcase of this PR, widening_mul is the
first dump that contains OVERFLOW. Otherwise, indeed the builtins, and match.pd
seems to have one transform that can produce IFN_MUL_OVERFLOW.