public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/64213] gimple-match.c:1523:6: error: ‘GIMPLE’ was not declared in this scope
Date: Tue, 09 Dec 2014 14:44:00 -0000	[thread overview]
Message-ID: <bug-64213-4-aEmjvu3Xmb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64213-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from uros at gcc dot gnu.org ---
Author: uros
Date: Tue Dec  9 14:44:06 2014
New Revision: 218518

URL: https://gcc.gnu.org/viewcvs?rev=218518&root=gcc&view=rev
Log:
    PR bootstrap/64213
    Revert:
    2014-11-28  H.J. Lu  <hongjiu.lu@intel.com>

    PR rtl-optimization/64037
    * combine.c (setup_incoming_promotions): Pass the argument
    before any promotions happen to promote_function_mode.

testsuite/ChangeLog:

    PR bootstrap/64213
    Revert:
    2014-11-28  H.J. Lu  <hongjiu.lu@intel.com>

    PR rtl-optimization/64037
    * g++.dg/pr64037.C: New test.


Removed:
    branches/gcc-4_8-branch/gcc/testsuite/g++.dg/pr64037.C
Modified:
    branches/gcc-4_8-branch/gcc/ChangeLog
    branches/gcc-4_8-branch/gcc/combine.c
    branches/gcc-4_8-branch/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2014-12-09 14:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-07 18:37 [Bug bootstrap/64213] New: " ubizjak at gmail dot com
2014-12-08 13:30 ` [Bug bootstrap/64213] " rguenth at gcc dot gnu.org
2014-12-08 20:23 ` ubizjak at gmail dot com
2014-12-09 11:29 ` ubizjak at gmail dot com
2014-12-09 11:41 ` rguenther at suse dot de
2014-12-09 14:35 ` uros at gcc dot gnu.org
2014-12-09 14:41 ` uros at gcc dot gnu.org
2014-12-09 14:44 ` uros at gcc dot gnu.org [this message]
2014-12-09 14:50 ` ubizjak at gmail dot com

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-64213-4-aEmjvu3Xmb@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).