This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: target macro->hook migration idea
- From: Mike Stump <mrs at apple dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gdr at integrable-solutions dot net, neil at daikokuya dot co dot uk, ghazi at caip dot rutgers dot edu, gcc at gcc dot gnu dot org, zack at codesourcery dot com
- Date: Thu, 24 Jul 2003 09:58:48 -0700
- Subject: Re: RFC: target macro->hook migration idea
On Tuesday, July 22, 2003, at 12:18 PM, DJ Delorie wrote:
you mean interface with "C++ virtual functions" ? :-D ;-)
If the target struct were a C++ class, that would make subtargets a
lot easier. But we're getting way ahead of ourselves ;-)
And you can use MI to do defaults of many different flavors, each
packages in their own headers.
class ELF {
virtual int has_section() { return 1; }
};
class ELF64 : public ELF {
...
};
class gas {
};
class Solaris {
};
class MyTarget : public ELF64, Solaris, gas {
};
Hookizing everything will make it simpler to convert everything to C++
later.
Bwaa ha ha... :-)