This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Converting tm.h macros to functions
- To: Neil Booth <neil at daikokuya dot demon dot co dot uk>, "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Subject: Re: Converting tm.h macros to functions
- From: Mark Mitchell <mark at codesourcery dot com>
- Date: Mon, 18 Jun 2001 12:18:06 -0700
- cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
> I was thinking of keeping the structures separate, to avoid the tedium
> of struct1.struct2.member. I don't think lumping them together buys
> you much.
>
In that case, I would just build one big structure. There is definitely
an abstraction called "the target" that has all these properties. It
makes sense for that mental abstraction to appear as a code abstraction.
I was thinking of a "the target" as the conjuction of "how you output
assembly code" and "what debugging format you use" and "whether or not
you use setjmp/longjmp exceptions" and so forth. You can separate
the conjuction into separate structures, or just mush them all together.
But, conceptual things should ideally map one-to-one on code things.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com