[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-28 02:34 --- Assigning to Daniel Berlin by his request. -- What|Removed |Added AssignedTo|mark at

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread dberlin at dberlin dot org
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-09-28 02:31 --- Subject: Re: [4.1 Regression] C++ generates incorrect overlapping fields On Wed, 2005-09-28 at 02:06 +, mark at codesourcery dot com wrote: > --- Additional Comments From mark at codesource

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-09-28 02:06 --- Subject: Re: [4.1 Regression] C++ generates incorrect overlapping fields dberlin at gcc dot gnu dot org wrote: > However, the questions still remains, what is the offset supposed to be > relative to? The

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread dberlin at gcc dot gnu dot org
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-09-28 02:03 --- I meant the next field of *B* was a type_decl fields unsigned SI size unit size align 32 symtab 0 alias set -1> unsigned virtual SI file /home/dbe

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread mark at codesourcery dot com
--- Additional Comments From mark at codesourcery dot com 2005-09-27 21:13 --- Subject: Re: [4.1 Regression] C++ generates incorrect overlapping fields dberlin at gcc dot gnu dot org wrote: > --- Additional Comments From dberlin at gcc dot gnu dot org 2005-09-27 > 20:42 ---

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread dberlin at gcc dot gnu dot org
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-09-27 20:42 --- We have a var of type C named D.2117 unit size align 32 symtab 0 alias set 21 fields ignored decl_6 BLK file /home/dberlin/22488.cc line 18 size

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-27 Thread mmitchel at gcc dot gnu dot org
--- Additional Comments From mmitchel at gcc dot gnu dot org 2005-09-27 16:32 --- I don't see what the alleged front-end bug is in this PR. The layout I would expect for C on IA32 GNU/Linux would be: 0: B's vptr 4: i0 8: i1 12: c 16: A's vptr 20: i 24: c0 25: c1 That is exactly what I

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-18 Thread mmitchel at gcc dot gnu dot org
-- What|Removed |Added AssignedTo|unassigned at gcc dot gnu |mark at codesourcery dot com |dot org | Status|NEW

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-18 Thread rguenth at gcc dot gnu dot org
--- Additional Comments From rguenth at gcc dot gnu dot org 2005-09-18 15:39 --- *** Bug 23949 has been marked as a duplicate of this bug. *** -- What|Removed |Added

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-05 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-05 14:20 --- And here is a testcase for 64bits: struct S02 { bool V01, V02; }; struct S03 {unsigned char V03; int V04; }; struct S05 { static void F01 ( int &P01, void *P02, void *P03 ); }; struct S07 {}; struct S0

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-09-05 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-09-05 14:19 --- *** Bug 23729 has been marked as a duplicate of this bug. *** -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22488

[Bug c++/22488] [4.1 Regression] C++ generates incorrect overlapping fields

2005-08-29 Thread dberlin at gcc dot gnu dot org
--- Additional Comments From dberlin at gcc dot gnu dot org 2005-08-29 13:57 --- I've changed the summary to match what the actual bug appears to be, at least until a C++ person tells us whether it's supposed to be generating these overlaps or not. -- What|Removed