public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6822: GCC 3.1.1 - Internal compiler error in extract_insn, at recog.c:2132
Date: Tue, 28 May 2002 16:36:00 -0000	[thread overview]
Message-ID: <20020528233601.9469.qmail@sources.redhat.com> (raw)

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

From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: "Glen Nakamura" <glen@imodulo.com>
Cc: <gcc-gnats@gcc.gnu.org>,
	<gcc-bugs@gcc.gnu.org>
Subject: Re: optimization/6822: GCC 3.1.1 - Internal compiler error in extract_insn, at recog.c:2132
Date: Wed, 29 May 2002 01:29:35 +0200

 > Previously, unsigned X < 128 would be converted to unsigned X <= 127 and
 > then optimized to signed X >= 0.  After changing the order of the
 > transformations, the compiler only reduces the expression to X <= 127 ???
 > The result is the reported ICE.  This could very well be a latent bug
 > in other parts of the compiler, but it seems the change results in missed
 > opportunities to simplify expressions.  I'll post an alternative patch
 > in my next message...
 
 I was almost sure to have checked the cross-dependencies between the various
 blocks of code, but I overlooked this 'unsigned <= 0x7fffffff' thing... Your
 patch is obviously better than mine in order to fix this chicken-and-egg
 problem.
 
 May I suggest you to add thorough cross-comments to the code ? I see you did
 so for the second optimization and I think it would be nice to do it for the
 first one too (saying that the current location of the optimization causes
 the second one to be altered).
 
 It looks like this doesn't fit with the GCC policy on the matter, but it
 could also be worth leaving the original code inside an #if 0/#endif or a
 comment.
 
 --
 Eric Botcazou
 ebotcazou@multimania.com
 


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

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-28 16:36 Eric Botcazou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-02 13:06 Glen Nakamura
2002-06-02 12:36 Richard Henderson
2002-05-30 16:56 rth
2002-05-29 12:16 Richard Henderson
2002-05-29 10:36 Richard Henderson
2002-05-29  9:44 Glen Nakamura
2002-05-29  9:16 Eric Botcazou
2002-05-29  0:46 Glen Nakamura
2002-05-28 18:16 Glen Nakamura
2002-05-28 17:16 Eric Botcazou
2002-05-28 11:00 Richard Henderson
2002-05-28  8:16 Glen Nakamura
2002-05-28  7:10 Glen Nakamura
2002-05-26 16:46 paolo
2002-05-26 12:26 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=20020528233601.9469.qmail@sources.redhat.com \
    --to=ebotcazou@libertysurf.fr \
    --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).