public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Glen Nakamura <glen@imodulo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6713: Regression wrt 3.0.4: g++ -O2 leads to seg fault at run time
Date: Wed, 22 May 2002 19:36:00 -0000	[thread overview]
Message-ID: <20020523023601.21005.qmail@sources.redhat.com> (raw)

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

From: Glen Nakamura <glen@imodulo.com>
To: gcc-gnats@gcc.gnu.org, mark@ecriticalinc.com, pcarlini@unitus.it,
	gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:  
Subject: Re: optimization/6713: Regression wrt 3.0.4: g++ -O2 leads to seg fault at run time
Date: Wed, 22 May 2002 16:31:39 -1000

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6713
 
 FYI: the problem also goes away when compiling w/ -O2 -fno-strength-reduce.
 I'm not sure how it's supposed to work, but strength_reduce() in loop.c
 eliminates reg 60 but leaves a REG_EQUAL note referring to it within the loop.
 I think this REG_EQUAL note is cause of the problem...  If I eliminate it,
 the problem goes away.  BTW, changing ++i to i++ in the for loop avoids the
 problem since the REG_EQUAL note is not emitted in that case.
 
 Any thoughts on how to fix this?  I'm not familiar enough with the loop
 optimizer to produce a proper patch.
 
 - Glen Nakamura
 
 
 [snip]
 giv at 482 reduced to (reg 135)
 giv at 480 reduced to (reg 135)
 biv 60 was eliminated.
 Reg 60: biv eliminated
 [snip]
 (note 351 591 492 NOTE_INSN_LOOP_BEG)
 [snip]
 (note 529 474 482 [bb 6] NOTE_INSN_BASIC_BLOCK)
 
 (insn 482 529 588 (set (reg/s/f:SI 111)
         (reg/f:SI 135)) -1 (nil)
     (expr_list:REG_EQUAL (plus:SI (reg/v:SI 60)   <<< PROBLEM NOTE???
             (const_int 1 [0x1]))
         (nil)))
 
 (insn 588 482 489 (set (reg/s/f:SI 111)
         (reg/f:SI 135)) -1 (nil)
     (nil))
 
 (note 489 588 490 0x40660980 NOTE_INSN_BLOCK_END)
 [snip]
 (note 497 408 499 NOTE_INSN_LOOP_END)
 [snip]
 


             reply	other threads:[~2002-05-23  2:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22 19:36 Glen Nakamura [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-04  8:54 paolo
2002-05-18  2:26 Paolo Carlini

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