public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64274] [5.0 Regression][ARM] gcc.target/arm/fixed-point-exec.c ICE in fold_binary_loc
Date: Fri, 12 Dec 2014 09:37:00 -0000	[thread overview]
Message-ID: <bug-64274-4-H2MbX7jTSp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64274-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64274

--- Comment #2 from ktkachov at gcc dot gnu.org ---
(In reply to Marek Polacek from comment #1)
> Does the following fix it?
> 
> diff --git a/gcc/fold-const.c b/gcc/fold-const.c
> index 7b68bea..34f5a6b 100644
> --- a/gcc/fold-const.c
> +++ b/gcc/fold-const.c
> @@ -10082,7 +10082,8 @@ fold_binary_loc (location_t loc,
>           /* Reassociate (plus (plus (mult) (foo)) (mult)) as
>              (plus (plus (mult) (mult)) (foo)) so that we can
>              take advantage of the factoring cases below.  */
> -         if (TYPE_OVERFLOW_WRAPS (type)
> +         if (ANY_INTEGRAL_TYPE_P (type)
> +             && TYPE_OVERFLOW_WRAPS (type)
>               && (((TREE_CODE (arg0) == PLUS_EXPR
>                     || TREE_CODE (arg0) == MINUS_EXPR)
>                    && TREE_CODE (arg1) == MULT_EXPR)

Yes, thanks. I'll bootstrap this on arm-none-linux-gnueabihf it you'd like


  parent reply	other threads:[~2014-12-12  9:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11 17:43 [Bug middle-end/64274] New: " ktkachov at gcc dot gnu.org
2014-12-11 18:05 ` [Bug middle-end/64274] " mpolacek at gcc dot gnu.org
2014-12-12  9:37 ` ktkachov at gcc dot gnu.org [this message]
2014-12-12  9:38 ` rguenth at gcc dot gnu.org
2014-12-12 14:03 ` mpolacek at gcc dot gnu.org
2014-12-12 14:03 ` mpolacek at gcc dot gnu.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=bug-64274-4-H2MbX7jTSp@http.gcc.gnu.org/bugzilla/ \
    --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).