public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Lipe <robertl@dgii.com>
To: egcs@cygnus.com
Subject: bug in expr.c?
Date: Mon, 09 Feb 1998 21:34:00 -0000	[thread overview]
Message-ID: <19980209233414.16572@dgii.com> (raw)

I was cleaning up warnings expr.c and believe this to be a bug.   Can
anyone that actually understands this confirm or deny this?

expand_assignment()

      if (TREE_CODE (to) == COMPONENT_REF
          && TREE_READONLY (TREE_OPERAND (to, 1)))
        {
          if (offset = 0)
            to_rtx = copy_rtx (to_rtx);

          RTX_UNCHANGING_P (to_rtx) = 1;
        }

That copy_rtx will never ever be called, right?

Is the "obvious" fix of "offset == 0" correct?

Thanx,
RJL

             reply	other threads:[~1998-02-09 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-09 21:34 Robert Lipe [this message]
1998-02-10  3:34 ` Jeffrey A Law
1998-02-10 14:45 Mike Stump
1998-02-12 20:07 Mike Stump
1998-02-13  2:04 ` Robert Lipe

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=19980209233414.16572@dgii.com \
    --to=robertl@dgii.com \
    --cc=egcs@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).