public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: Michael_Collison@iris.com
Cc: egcs@cygnus.com, gcc2@cygnus.com
Subject: Re: Problem in 'reload_cse_regno_equal_p'
Date: Tue, 28 Apr 1998 14:10:00 -0000	[thread overview]
Message-ID: <199804282109.WAA14618@phal.cygnus.co.uk> (raw)
In-Reply-To: <852565F4.005648AF.00@arista.iris.com>

> It seems that the code for the 'for' loop is incorrect. Why is 'x' being
> set
> equal to 'XEXP(x,1)' everytime thru the loop? The code seems to be assuming
> that it will hit a null pointer and things will be okay with the check at
> the next line. Is it okay for the code to assume this?

Yes, it is.  Look at the comment in front of the reg_values declaration.
There should only be EXPR_LISTs of values.  So the real question is,
where and why has the raw SYMBOL_REF been added?

  reply	other threads:[~1998-04-28 14:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-04-28 11:00 Michael_Collison
1998-04-28 14:10 ` Joern Rennecke [this message]
1998-04-29 15:21 Michael_Collison

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=199804282109.WAA14618@phal.cygnus.co.uk \
    --to=amylaar@cygnus.co.uk \
    --cc=Michael_Collison@iris.com \
    --cc=egcs@cygnus.com \
    --cc=gcc2@cygnus.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).