This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug preprocessor/81419] GCC wrongly suggests function-like macro as fixit hint for undefined object-like macro


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81419

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2017-08-18
                 CC|                            |msebor at gcc dot gnu.org
           See Also|                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=80567,
                   |                            |https://gcc.gnu.org/bugzill
                   |                            |a/show_bug.cgi?id=80684
     Ever confirmed|0                           |1

--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed.  There are few other similar bugs for these fix-it hints (e.g.,
pr80567 or pr80684).  I haven't looked at the implementation but from the
symptoms it feels like the problem is that the search doesn't fully consider
the context in which the undeclared is used.   I.e., it doesn't distinguish
between a function call, other kinds of expressions, a type, or even a keyword,
etc.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]