[Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
------- Additional Comments From wilson at specifixinc dot com 2004-01-22 05:21 -------
Subject: Re: [3.4/3.5 regression] [ia64] ICE in push_secondary_reload
zack at codesourcery dot com wrote:
> ... excuse me for having bigger problems on my plate right now. Not
> to mention that none of this is reproducible on any target I can
> conveniently test on.
The simple fact is that you have broken the IA-64 compiler a number of
times, and you have not always been responsive to fixing the problems
you have caused. This is very annoying. There are many people using
the IA-64 port, and you inconvience them everytime you break it.
I have important work to do also, but instead I am forced to do your
work for you, and I am not happy about this.
If you aren't going to try to do IA-64 work properly, then you could at
least post patches for review instead of just blindly checking them in
and waiting to see what breaks. Or you could voluntarily revert patches
when it is proven that they don't work. This is much more friendly to
the rest of us, particularly those of us using the IA-64 gcc port for
real work.
debian linux is and always has been free. If you have an IA-64 machine,
it should be easy to install debian on it.
>>However, for a MEM, this means that we are passing an operand to the
>>predicate that may appear to be invalid, but is valid because it has
>>already been reloaded.
Maybe the issue is that it hasn't been reloaded yet? In any case, we
are in the middle of reload, so we are guaranteed that a MEM is going to
be OK whether it looks OK or not.
> This is insane. Clearly the bug is that overlapping operands can
> occur in the first place.
It has always worked this way. I know this is lame, but one should
never underestimate the difficulty of trying to change how reload works.
It is much easier to change all md file than to change reload. I
think there is an important reason why it works this way, but it
probably isn't possible to figure it out without spending an
unreasonable amount of time messing with the code.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Reply to: