This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
- From: "wilson at specifixinc dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Jan 2004 22:17:07 -0000
- Subject: [Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
- References: <20040117230657.13722.schwab@suse.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From wilson at specifixinc dot com 2004-01-22 22:17 -------
Subject: Re: [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
zack at codesourcery dot com wrote:
> The implication of what you are saying above is that you don't think
> anyone without access to an ia64-linux box should be allowed to touch
> the ia64 back end, which I think is bad policy.
This is one way to solve the problem, but not the only way. I mention
it because I think it is the most expedient. Another solution would be
for you to build an ia64-hpux Ada compiler. Another solution is for you
to voluntarily revert patches when it is discovered that they don't
work. Another solution is for you to ask for help testing patches
before checking them in.
> to find problems - but my experience is that everyone ignores me when
> I ask for a second opinion on my patches, so I don't expect this to
> help much.
I don't ignore IA-64 backend patches, though I am sometimes a week or so
behind on reading gcc-patches. I wouldn't mind if you cc'ed me on IA-64
backend patches so that I would see them sooner.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722