public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.com>
To: rth@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/8165: builtin string functions SEGV on alpha-pc-linux-gnu at -O2
Date: Sat, 12 Oct 2002 11:46:00 -0000	[thread overview]
Message-ID: <20021012184601.4835.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/8165; it has been noted by GNATS.

From: Glen Nakamura <glen@imodulo.com>
To: Richard Henderson <rth@redhat.com>, gcc-gnats@gcc.gnu.org,
	gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc:  
Subject: Re: optimization/8165: builtin string functions SEGV on alpha-pc-linux-gnu at -O2
Date: Sat, 12 Oct 2002 08:39:25 -1000

 On Fri, Oct 11, 2002 at 05:51:43PM -0700, Richard Henderson wrote:
 > I guess your original patch is probably correct.  I was 
 > focused so much on the LO_SUM/HIGH simplification that
 > I missed the fact that we were failing to process the
 > internal regs of the LO_SUM at all.
 
 Looking at try_replace_reg() again, I noticed that the REG_EQUAL note
 isn't always replaced.  Is the "else" really okay?
 
 
 static int
 try_replace_reg (from, to, insn)
      rtx from, to, insn;
 {
   rtx note = find_reg_equal_equiv_note (insn);
   ...
 
   if (!success && set && reg_mentioned_p (from, SET_SRC (set)))
     {
       ...
 
       /* If we've failed to do replacement, have a single SET, and don't already
 	 have a note, add a REG_EQUAL note to not lose information.  */
       if (!success && note == 0 && set != 0)
 	note = set_unique_reg_note (insn, REG_EQUAL, copy_rtx (src));
     }
 
   /* If there is already a NOTE, update the expression in it with our
      replacement.  */
   else if (note != 0)
   ^^^^
     XEXP (note, 0) = simplify_replace_rtx (XEXP (note, 0), from, to);
 


             reply	other threads:[~2002-10-12 18:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-12 11:46 Glen Nakamura [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-14 11:16 Richard Henderson
2002-10-11 17:56 Richard Henderson
2002-10-11 16:26 Glen Nakamura
2002-10-11 16:13 rth
2002-10-11 15:46 Richard Henderson
2002-10-08 16:16 Glen Nakamura
2002-10-08 15:26 Richard Henderson
2002-10-07 18:26 Glen Nakamura
2002-10-07 17:56 glen

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=20021012184601.4835.qmail@sources.redhat.com \
    --to=glen@imodulo.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=rth@gcc.gnu.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 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).