On Mon, Mar 23, 2009 at 7:28 PM, Steve Ellcey <[email protected]> wrote:
> I think
> depreciating Itanium1 tuning for 4.4 and removing it in 4.5 is
> reasonable. Code generated and tuned for Itanium2 should run fine on
> Itanium1 (Merced). It won't be scheduled optimally of course, but it
> should run correctly.
(...)
> I will approve this patch, but it should say "Itanium1 tuning support"
> or something like that. The code will run on Itanium1, just not
> optimally.
Like so (with same changelog). I'll commit this before the end of the
week to the gcc-4_4-branch if no-one objects. Bootstrapped and tested
on ia64 with gcc-4_4-branch.
For gcc 4.5, should I wait with posting the cleanup patch until the
end of the development cycle, or can we go ahead and clean things up
now in stage 1?
Ciao!
Steven
* config/ia64/ia64.c (ia64_handle_option): Inform user that Itanium1
support is deprecated if the -mtune value is set to an Itanium1
variant.
Index: config/ia64/ia64.c
===================================================================
--- config/ia64/ia64.c (revision 145211)
+++ config/ia64/ia64.c (working copy)
@@ -5212,6 +5212,8 @@ fix_range (const char *const_str)
static bool
ia64_handle_option (size_t code, const char *arg, int value)
{
+ static bool warned_itanium1_deprecated;
+
switch (code)
{
case OPT_mfixed_range_:
@@ -5245,6 +5247,16 @@ ia64_handle_option (size_t code, const c
if (!strcmp (arg, processor_alias_table[i].name))
{
ia64_tune = processor_alias_table[i].processor;
+ if (ia64_tune == PROCESSOR_ITANIUM
+ && ! warned_itanium1_deprecated)
+ {
+ inform (0,
+ "value %<%s%> for -mtune= switch is deprecated",
+ arg);
+ inform (0, "GCC 4.4 is the last release with "
+ "Itanium1 tuning support");
+ warned_itanium1_deprecated = true;
+ }
break;
}
if (i == pta_size)
