This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2b
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: Michael Meissner <meissner at linux dot vnet dot ibm dot com>, gcc-patches at gcc dot gnu dot org, bergner at vnet dot ibm dot com, segher at kernel dot crashing dot org, iain at codesourcery dot com, andreast-list at fgznet dot ch
- Date: Wed, 3 Oct 2012 21:42:05 -0400
- Subject: Re: [PATCH] Rs6000 infrastructure cleanup (switches), revised patch #2b
- References: <20120912224303.GA19348@ibm-tiger.the-meissners.org> <20120917195131.GA22648@ibm-tiger.the-meissners.org> <CAGWvnykaJM0LFiwVJRcoay4uVJtrFR-V8G=_aK6=4VQygmAx0w@mail.gmail.com> <20120920195755.GA18581@ibm-tiger.the-meissners.org> <20120927224228.GA24889@ibm-tiger.the-meissners.org>
@@ -1115,7 +1118,8 @@ static const struct attribute_spec rs600
{ NULL, 0, 0, false, false, false, NULL, false }
};
-#ifndef MASK_STRICT_ALIGN
+#ifndef OPTION_MASK_STRICT_ALIGN
+#define OPTION_MASK_STRICT_ALIGN 0
#define MASK_STRICT_ALIGN 0
#endif
#ifndef TARGET_PROFILE_KERNEL
Why does this fragment define OPTION_MASK_STRICT_ALIGN but does not
remove definition of MASK_STRICT_ALIGN?
Similarly for
-#ifndef MASK_64BIT
+#ifndef OPTION_MASK_64BIT
+#define OPTION_MASK_64BIT 0
#define MASK_64BIT 0
#endif
Why define both OPTION_MASK_64BIT and MASK_64BIT?
And
+/* Map OPTION_<xxx> back into TARGET_<xxx> options in rs6000_isa_flags. */
Why set up correspondence for all OPTION_xxx flags back to TARGET_xxx flags?
Thanks, David