https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
Georg-Johann Lay changed:
What|Removed |Added
Last reconfirmed|2012-01-07 00:00:00 |2024-8-2
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
Tim Turner changed:
What|Removed |Added
CC||timturnerc at yahoo dot com
--- Comment #15
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
--- Comment #14 from Matthijs Kooijman ---
Thanks for the additional explanations!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
--- Comment #13 from Georg-Johann Lay ---
(In reply to Matthijs Kooijman from comment #12)
> Apologies if this is an obvious question, but I'm not familiar with gcc/g++
> internals. Georg-Johann, you say this requires address space support in c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
Matthijs Kooijman changed:
What|Removed |Added
CC||matthijs at stdin dot nl
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
Georg-Johann Lay changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
--- Comment #10 from Oscar García ---
This problem can be mitigated using "pointer to interfaces".
Instead of:
class A
{
public:
A();
void FncEatingVTableRamA();
void FncEatingVTableRamB();
void FncEatingVTableRamC();
void FncEatingVTableRamD()
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
Jackie Rosen changed:
What|Removed |Added
CC||jackie.rosen at hushmail dot
com
--- Comm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43745
Georg-Johann Lay changed:
What|Removed |Added
Component|target |c++
--- Comment #8 from Georg-Johann L
