[Bug c/80892] [8 regression] -Wfloat-conversion now warns about non-floats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80892 Martin Sebor changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Martin Sebor --- Fixed in r248852.
[Bug c/80892] [8 regression] -Wfloat-conversion now warns about non-floats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80892 --- Comment #3 from Martin Sebor --- Author: msebor Date: Sat Jun 3 02:49:30 2017 New Revision: 248852 URL: https://gcc.gnu.org/viewcvs?rev=248852&root=gcc&view=rev Log: PR c/80892 - -Wfloat-conversion now warns about non-floats gcc/c-family/ChangeLog: PR c/80892 * c-warn.c (conversion_warning): Use -Wconversion for integer conversion and -Wfloat-conversion for floating one. gcc/testsuite/ChangeLog: PR c/80892 * c-c++-common/Wfloat-conversion-2.c: New test. Modified: trunk/gcc/c-family/ChangeLog trunk/gcc/c-family/c-warn.c trunk/gcc/testsuite/ChangeLog
[Bug c/80892] [8 regression] -Wfloat-conversion now warns about non-floats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80892 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #2 from Martin Sebor --- Patch: https://gcc.gnu.org/ml/gcc-patches/2017-05/msg02288.html
[Bug c/80892] [8 regression] -Wfloat-conversion now warns about non-floats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80892 Richard Biener changed: What|Removed |Added Target Milestone|--- |8.0
[Bug c/80892] [8 regression] -Wfloat-conversion now warns about non-floats
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80892 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed||2017-05-26 Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Martin Sebor --- Confirmed: $ cat t.c && gcc -S -Wfloat-conversion t.c void f (char); void g (unsigned long x) { f (x); } t.c: In function ‘g’: t.c:5:6: warning: conversion from ‘long unsigned int’ to ‘char’ may change value [-Wfloat-conversion] f (x); ^ The conversion changes were committed in r248431. They weren't intended to change how warnings are controlled so this is a bug.