This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
target_flags
- From: Mike Stump <mrs at apple dot com>
- To: gcc at gcc dot gnu dot org
- Date: Mon, 10 Mar 2003 12:22:33 -0800
- Subject: target_flags
Ok, so I am working on a port (rs6000) that is out of target_flags by
about 4 flags (in my tree). :-( What do I do now?
Solutions come to mind,
1 Give up, go home, to hard to fix
2 long long
4 int[2]
8 bitmap.h
16 remove extraneous target_flags
32 don't use target_flags, just hide them elsewhere (flag_opt2,
flag_opt3)
64 nest target flags so that other bits have multiple meanings
depending upon what other target_flags bits are set.
long long appears nice, but -Werror, -Wlong-long and friends kill it
4 is no better than 8.
I think I like 8 the best, the impact would be, uhm, extensive. The
impact of even 2 would be large (-0x02 -> -0x02LL in all ports). For
8, I think MASK_TARGET_OPT1 type things ought to take bit positions.
The concept of multiple bits as a C constant fades away with 4 and 8.
:-(