All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jessica Han" <jessica@cup.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: optimization/3783
Date: Tue, 04 Sep 2001 20:33:04 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805119@msgid-missing> (raw)

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%26pr783%26database=gcc
 It seems this problem occurs only when we have POST_INC addressing mode.
With POST_INC, for rtl "set reg351, reg328 PLUS 1", attempt_auto_inc
(flow.c) will change reg328 into reg351 as an operand of POST_INC, but leave
the "PLUS" as is. Thus the RTL becomes "set reg 351, reg351 PLUS 1" and
causes the infinite recursion in canon_rtx. If I substitute "reg328 PLUS 1"
with POST_INC reg351, the testcase attached in GNAT will pass at compile
time.
   The fix I did is in attempt_auto_inc:
  <       validate_change (incr, &XEXP (y, opnum), q, 1);
  ---
  >       validate_change (incr, &y, inc, 1);
Is this the right thing to do? Thanks.




             reply	other threads:[~2001-09-04 20:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-04 20:33 Jessica Han [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-01 22:02 [Linux-ia64] Re: optimization/3783 Steve Ellcey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105590698805119@msgid-missing \
    --to=jessica@cup.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.