This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Deprecating Itanium1 for GCC 4.4
- From: Andi Kleen <andi at firstfloor dot org>
- To: Steven Bosscher <stevenb dot gcc at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, gcc mailing list <gcc at gcc dot gnu dot org>, Jim Wilson <wilson at tuliptree dot org>, sje at cup dot hp dot com, "H.J. Lu" <hjl dot tools at gmail dot com>, Gerald Pfeifer <gerald at pfeifer dot com>
- Date: Fri, 20 Mar 2009 10:31:07 +0100
- Subject: Re: Deprecating Itanium1 for GCC 4.4
- References: <571f6b510903150916qa6ec3a4o6a85c09698ee0bb@mail.gmail.com> <alpine.LSU.1.99.0903151823370.20299@acrux.dbai.tuwien.ac.at> <571f6b510903191624l4e5fa9b4q87cdc1fd14b87ff8@mail.gmail.com>
Steven Bosscher <stevenb.gcc@gmail.com> writes:
> case OPT_mfixed_range_:
> @@ -5245,6 +5247,13 @@ ia64_handle_option (size_t code, const char *arg,
> if (!strcmp (arg, processor_alias_table[i].name))
> {
> ia64_tune = processor_alias_table[i].processor;
> + if (ia64_tune == PROCESSOR_ITANIUM
> + && ! warned_merced_deprecated)
> + {
> + inform ("value %<%s%> for -mtune= switch is deprecated", arg);
> + inform ("GCC 4.4 is the last release with Itanium1 support");
"... with Itanium1 tuning support"?
I assume it will be still possible to generate executables that work
there, just not tuned. iirc there are new instructions in I2, but I
assume you don't plan to drop the code to not generate those, just the
scheduling descriptions.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.