On 02/25/2013 06:25 PM, Jason Merrill wrote:
On 02/25/2013 06:24 PM, Jason Merrill wrote:
I think my preference would be to avoid calling fixed_type_or_null at
all when we're in a template. I already changed
resolves_to_fixed_type_p that way, now we need to fix build_vtbl_ref_1.
Oops, now I s
On 02/25/2013 06:25 PM, Jason Merrill wrote:
On 02/25/2013 06:24 PM, Jason Merrill wrote:
I think my preference would be to avoid calling fixed_type_or_null at
all when we're in a template. I already changed
resolves_to_fixed_type_p that way, now we need to fix build_vtbl_ref_1.
Oops, now I s
On 02/25/2013 06:24 PM, Jason Merrill wrote:
I think my preference would be to avoid calling fixed_type_or_null at
all when we're in a template. I already changed
resolves_to_fixed_type_p that way, now we need to fix build_vtbl_ref_1.
Oops, now I see the discussion on the PR. I'll take a look
I think my preference would be to avoid calling fixed_type_or_null at
all when we're in a template. I already changed
resolves_to_fixed_type_p that way, now we need to fix build_vtbl_ref_1.
For post 4.8 we might avoid messing with vtables at all when we're in
a template.
Jason
Hi,
Please see details on Bugzilla.
Tested x86_64-unknown-linux-gnu without regressions.
gcc/testsuite/ChangeLog
2012-02-25 Fabien Chêne
PR c++/56243
* g++.dg/cpp0x/pr56243.C: New.
gcc/cp/ChangeLog
2012-02-25 Fabien Chêne
PR c++/56243
* class.c (fixed_ty
