| commit | c961ab09d2bc312d6d0ee2f6de5af39dc574d464 | |
| author | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 7 Feb 2018 01:52:48 +0000 (7 01:52 +0000) | ||
| committer | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 7 Feb 2018 01:52:48 +0000 (7 01:52 +0000) | ||
| tree | 24d63e86412abc324b20ce986151d07c70bf01a2 | treesnapshot (tar.gz zip) |
| parent | 60d73abd796158dff8231ba3a1b7c54d9fd6fbe1 | commitdiff |
compiler: make single Btype for methods table of identical interface type
Normally we ensure to build a single Btype for identical types.
We did not do this for methods table of identical interface
types, however. If there are two identical interface type I, I2,
they have the same Btype BI, but different Btypes for their
methods tables, BM and BM2. From the backend's point of view
only one of them is linked to BI. This can cause inconsitency
in the backend's type system, like unresolved placeholder. This
CL ensures we create a single Btype for methods table of
identical interface type.
Reviewed-on: https://go-review.googlesource.com/92436
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@257436 138bc75d-0d04-0410-961f-82ee72b054a4
Normally we ensure to build a single Btype for identical types.
We did not do this for methods table of identical interface
types, however. If there are two identical interface type I, I2,
they have the same Btype BI, but different Btypes for their
methods tables, BM and BM2. From the backend's point of view
only one of them is linked to BI. This can cause inconsitency
in the backend's type system, like unresolved placeholder. This
CL ensures we create a single Btype for methods table of
identical interface type.
Reviewed-on: https://go-review.googlesource.com/92436
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@257436 138bc75d-0d04-0410-961f-82ee72b054a4
| gcc/go/gofrontend/MERGE | diffblobblamehistory | |
| gcc/go/gofrontend/types.cc | diffblobblamehistory | |
| gcc/go/gofrontend/types.h | diffblobblamehistory |