public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/30338] [4.3 Regression] infinite loop in maybe_canonicalize_comparison
Date: Sun, 31 Dec 2006 16:49:00 -0000	[thread overview]
Message-ID: <20061231164904.1720.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30338-9596@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from pinskia at gcc dot gnu dot org  2006-12-31 16:49 -------
(In reply to comment #5)
> (that needs to read
> 
>         return fold_build1 (BIT_NOT_EXPR, type, op1);

No it should read:
return fold_build1 (BIT_NOT_EXPR, type, fold_convert (type, arg1) );

There are a couple more issues like this in fold-const.c with BIT_NOT_EXPR
folding.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30338


  parent reply	other threads:[~2006-12-31 16:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-31 11:38 [Bug c/30338] New: Segmentation fault for legal code with -Os -m32 dcb314 at hotmail dot com
2006-12-31 11:40 ` [Bug c/30338] " dcb314 at hotmail dot com
2006-12-31 11:51 ` [Bug middle-end/30338] [4.3 Regression] infinite loop in maybe_canonicalize_comparison pinskia at gcc dot gnu dot org
2006-12-31 11:57 ` rguenth at gcc dot gnu dot org
2006-12-31 12:28 ` rguenth at gcc dot gnu dot org
2006-12-31 12:57 ` rguenth at gcc dot gnu dot org
2006-12-31 14:05 ` rguenth at gcc dot gnu dot org
2006-12-31 16:49 ` pinskia at gcc dot gnu dot org [this message]
2010-07-08 21:50 ` bergner at gcc dot gnu dot org
2010-07-09  8:10 ` rguenther at suse dot de
2010-07-09 14:37 ` bergner at gcc dot gnu dot org

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=20061231164904.1720.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).