[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-12-02 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 --- Comment #15 from Richard Guenther rguenth at gcc dot gnu.org 2010-12-02 12:24:50 UTC --- Author: rguenth Date: Thu Dec 2 12:24:46 2010 New Revision: 167367 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=167367 Log: 2010-12-02 Richard

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-12-02 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-11-26 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 --- Comment #12 from Richard Guenther rguenth at gcc dot gnu.org 2010-11-26 16:29:53 UTC --- I'd like to hear opinions from C and C++ FE people as to why the current state illustrated in comment #6 makes sense and if the behavior can be

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-11-26 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 --- Comment #13 from Richard Guenther rguenth at gcc dot gnu.org 2010-11-26 17:06:25 UTC --- Testcase: cat gcc/testsuite/g++.dg/lto/20101126-1_0.C typedef struct { int i; } T1; typedef T1 T2; extern T1 a; extern T2 b; int main() { return a.i +

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-11-26 Thread joseph at codesourcery dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 --- Comment #14 from joseph at codesourcery dot com joseph at codesourcery dot com 2010-11-26 18:40:15 UTC --- On Fri, 26 Nov 2010, rguenth at gcc dot gnu.org wrote: I'd like to hear opinions from C and C++ FE people as to why the current

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-10-14 Thread hubicka at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 --- Comment #11 from Jan Hubicka hubicka at gcc dot gnu.org 2010-10-15 02:39:00 UTC --- Richard, any hope for a clean fix or shall we go with the hack above for next release?

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-10-02 Thread hubicka at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44871 Jan Hubicka hubicka at gcc dot gnu.org changed: What|Removed |Added Last reconfirmed|2010-07-08 14:47:48 |2010-10-02

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-07-09 Thread rguenth at gcc dot gnu dot org
--- Comment #7 from rguenth at gcc dot gnu dot org 2010-07-09 12:42 --- The hard part with changing the C frontend to behave like the C++ frontend is to preserve the debug info for the typedef. The C frontend consistently uses DECL_ORIGINAL_TYPE to refer to what a TYPE_DECL was

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-07-09 Thread rguenth at gcc dot gnu dot org
--- Comment #8 from rguenth at gcc dot gnu dot org 2010-07-09 12:52 --- The only difference I see for typedef struct { } T1; vs typedef struct X { } T1; when looking at its main variant (or recursively DECL_ORIGINAL_TYPE) is type_decl 0x75b2be60 X type record_type

[Bug c++/44871] Invalid type mismatches while merging C and C++ sources

2010-07-09 Thread rguenth at gcc dot gnu dot org
--- Comment #9 from rguenth at gcc dot gnu dot org 2010-07-09 13:01 --- The following seems to work at least for the testcase: Index: gcc/tree.c === --- gcc/tree.c (revision 161994) +++ gcc/tree.c (working copy) @@