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/54369] delayed-branch pass removes too many instructions Date: Sun, 02 Sep 2012 10:37:00 -0000 [thread overview] Message-ID: <bug-54369-4-jpCAqUyITy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54369-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54369 --- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-09-02 10:36:31 UTC --- Author: ebotcazou Date: Sun Sep 2 10:36:27 2012 New Revision: 190858 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=190858 Log: PR rtl-optimization/54369 * config/mips/mips.c (mips_reorg): Invoke cleanup_barriers before calling dbr_schedule. * config/sparc/sparc.c (sparc_reorg): Likewise. Modified: trunk/gcc/ChangeLog trunk/gcc/config/mips/mips.c trunk/gcc/config/sparc/sparc.c
next prev parent reply other threads:[~2012-09-02 10:37 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-24 18:17 [Bug rtl-optimization/54369] New: Delayed-branch pass in reorg.c " chaoyingfu at gcc dot gnu.org 2012-08-29 22:43 ` [Bug rtl-optimization/54369] " ebotcazou at gcc dot gnu.org 2012-08-31 0:31 ` sje at gcc dot gnu.org 2012-08-31 0:39 ` chaoyingfu at gcc dot gnu.org 2012-08-31 14:21 ` ebotcazou at gcc dot gnu.org 2012-08-31 18:17 ` sje at gcc dot gnu.org 2012-08-31 18:56 ` ebotcazou at gcc dot gnu.org 2012-09-01 8:17 ` rdsandiford at googlemail dot com 2012-09-01 9:22 ` ebotcazou at gcc dot gnu.org 2012-09-01 9:42 ` rdsandiford at googlemail dot com 2012-09-01 15:13 ` [Bug rtl-optimization/54369] delayed-branch pass " ebotcazou at gcc dot gnu.org 2012-09-02 10:37 ` ebotcazou at gcc dot gnu.org [this message] 2012-09-02 10:38 ` ebotcazou at gcc dot gnu.org 2012-09-02 10:39 ` ebotcazou at gcc dot gnu.org 2012-09-02 10:39 ` ebotcazou at gcc dot gnu.org 2012-09-02 10:39 ` ebotcazou at gcc dot gnu.org 2012-09-02 10:48 ` ebotcazou at gcc dot gnu.org 2014-02-16 10:00 ` jackie.rosen at hushmail 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-54369-4-jpCAqUyITy@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: linkBe 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).