public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/51667] [4.7 Regression] new FAIL: 27_io/basic_*stream/* execution test with -m32
Date: Tue, 27 Dec 2011 16:29:00 -0000	[thread overview]
Message-ID: <bug-51667-4-dMWQiLvavQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51667-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #17 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2011-12-27 16:25:52 UTC ---
Author: ebotcazou
Date: Tue Dec 27 16:25:43 2011
New Revision: 182694

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=182694
Log:
    PR rtl-optimization/51667
    * ree.c (insn_merge_code): Delete.
    (is_insn_merge_attempted): Likewise.
    (get_insn_status): Likewise.
    (set_insn_status): Likewise.
    (struct ext_cand): Add CODE and MODE fields.
    (combine_set_extend): Rename to...
    (combine_set_extension): ...this.  Use above fields and tidy up.
    (transform_ifelse): Likewise.
    (get_defs): Return the chain of definitions.
    (is_this_a_cmove): Merge into...
    (is_cond_copy_insn): ...this.  Return bool.
    (make_defs_and_copies_lists): Adjust calls to get_defs and simplify.
    (merge_def_and_ext): Adjust call to combine_set_extend.
    (combine_reaching_defs): Remove calls to {g|s}et_insn_status.
    (struct extend_info): Rename to...
    (struct re_info): ...this.  Add DEF_MAP field.
    (add_ext_candidate): Merge into...
    (add_removable_extension): ...this.  Adjust calls to get_defs.  Ensure
    reaching definitions are associated with only one kind of extension.
    (find_removable_extensions): Create and destroy the definition map.
    (find_and_remove_re): Return void.  Change 'long' variables to 'int'.
    Do not deal with is_insn_merge_attempted.

Added:
    trunk/gcc/testsuite/gcc.c-torture/execute/20111227-1.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/ree.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2011-12-27 16:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 16:48 [Bug libstdc++/51667] New: " dominiq at lps dot ens.fr
2011-12-23 17:12 ` [Bug libstdc++/51667] " dominiq at lps dot ens.fr
2011-12-23 18:15 ` ubizjak at gmail dot com
2011-12-24  9:10 ` ubizjak at gmail dot com
2011-12-24 10:46 ` paolo.carlini at oracle dot com
2011-12-24 10:51 ` [Bug tree-optimization/51667] " paolo.carlini at oracle dot com
2011-12-24 11:15 ` ebotcazou at gcc dot gnu.org
2011-12-24 12:23 ` ubizjak at gmail dot com
2011-12-24 12:40 ` ubizjak at gmail dot com
2011-12-24 12:47 ` [Bug rtl-optimization/51667] " ubizjak at gmail dot com
2011-12-24 12:58 ` ubizjak at gmail dot com
2011-12-24 13:49 ` ubizjak at gmail dot com
2011-12-24 13:52 ` ubizjak at gmail dot com
2011-12-24 14:12 ` ubizjak at gmail dot com
2011-12-24 18:23 ` ebotcazou at gcc dot gnu.org
2011-12-27  1:37 ` ebotcazou at gcc dot gnu.org
2011-12-27 12:13 ` dominiq at lps dot ens.fr
2011-12-27 16:29 ` ebotcazou at gcc dot gnu.org [this message]
2011-12-27 18:01 ` ebotcazou at gcc dot gnu.org
2011-12-28  9:14 ` 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-51667-4-dMWQiLvavQ@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).