This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/81668] LTO ODR warnings are not helpful
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 07 Aug 2017 23:37:52 +0000
- Subject: [Bug c++/81668] LTO ODR warnings are not helpful
- Auto-submitted: auto-generated
- References: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81668
Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu.org
--- Comment #6 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
> fts0pars.y:62:0: note: a field with different name is defined in another
> translation unit
Did you cut the above? It looks like a note without a previous warning. Also,
GCC will have trouble to point out the correct location when compiling a
generated file that contains linemarkers, unless the linemarkers exactly point
out to the original file AND the original file is available to read.
> ../include/violite.h:288:8: warning: type ‘struct st_vio’ violates the C++
> One Definition Rule [-Wodr]
> struct st_vio
> ^
> ../include/violite.h:288:0: note: a different type is defined in another
> translation unit
> struct st_vio
>
This seems a problem with location info that fails to point to the .c file
affected. One should never get column 0.