This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: pa reload problem
- To: rth at redhat dot com (Richard Henderson)
- Subject: Re: pa reload problem
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Date: Fri, 8 Dec 2000 17:05:21 -0500 (EST)
- Cc: alan at linuxcare dot com dot au, law at cygnus dot com, rhirst at linuxcare dot com, parisc-linux at thepuffingroup dot com, gcc-bugs at gcc dot gnu dot org
> On Wed, Dec 06, 2000 at 03:41:06PM -0500, John David Anglin wrote:
> > > (expr_list:REG_EQUIV (mem/u:SI (lo_sum:SI (reg/f:SI 309)
> > > (unspec:SI[
> > > (symbol_ref:SI ("constructor_max_index"))
> > > ] 0)) 0)
>
> This appears to be the same sort of bug as in compile/20001205-1.c
> except that an unspec is involved instead of an asm_operands.
>
> I wonder if the best solution is to avoid local-alloc creating
> REG_EQUIV notes for every little thing under the sun. Allow
> only general_operand or something.
I am wondering if side_effects_p should return 1 if it encounters
an UNSPEC. Currently, it just ignores it. This would prevent the
generation of the REG_EQUIV notes and I think resolve the problem.
However, it might have other side effects. Any thoughts on this?
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)