public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: law@redhat.com
To: David Edelsohn <dje@watson.ibm.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Load hoisting bug
Date: Fri, 07 Dec 2001 16:49:00 -0000	[thread overview]
Message-ID: <4453.1007770588@porcupine.cygnus.com> (raw)
In-Reply-To: Your message of Fri, 07 Dec 2001 19:00:56 EST. <200112080000.TAA22812@makai.watson.ibm.com>

  > 	We have not had enough fun with loop optimizations lately, so I
  > found one...
  > 
  > 	The divconst-3.c regression on AIX which appeared at the beginning
  > of November is due to GCC miscompiling itself.  The miscompilation is
  > caused by a loop optimization which was not safe.
[ ... ]
Note that the handling of hard registers in loops changed in early November.
I believe this is the patch:

        * loop.c (loop_regs_scan):  Don't invalidate PIC register.

You might try without that patch and see if this problem goes away.
jeff



  reply	other threads:[~2001-12-08  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 16:01 David Edelsohn
2001-12-07 16:49 ` law [this message]
2001-12-07 16:50   ` Richard Henderson
2001-12-13 10:42     ` David Edelsohn
2001-12-13 13:26       ` Richard Henderson
2001-12-07 16:49 ` Richard Henderson

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=4453.1007770588@porcupine.cygnus.com \
    --to=law@redhat.com \
    --cc=dje@watson.ibm.com \
    --cc=gcc@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).