public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kkojima at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/28126] gcc moves an expensive instruction outside of a conditional Date: Thu, 22 Jun 2006 04:46:00 -0000 [thread overview] Message-ID: <20060622041650.25124.qmail@sourceware.org> (raw) In-Reply-To: <bug-28126-12556@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from kkojima at gcc dot gnu dot org 2006-06-22 04:16 ------- Although I don't know much about the instruction scheduling, I had a similar problem on SH and it was workarounded with emitting blockage insns. The patch below might work for you, though I'm not sure if it's the right thing to do. Ian's comment in the gcc list http://gcc.gnu.org/ml/gcc/2006-06/msg00669.html suggests us that there are more than one problem. --- ORIG/gcc-4_1-branch/gcc/config/mips/mips.c 2006-06-20 10:53:21.000000000 +0900 +++ TMP/gcc-4_1-branch/gcc/config/mips/mips.c 2006-06-22 12:49:26.000000000 +0900 @@ -1995,6 +1995,7 @@ mips_legitimize_tls_address (rtx loc) case TLS_MODEL_INITIAL_EXEC: tmp1 = gen_reg_rtx (Pmode); tmp2 = mips_unspec_address (loc, SYMBOL_GOTTPREL); + emit_insn (gen_blockage ()); if (Pmode == DImode) { emit_insn (gen_tls_get_tp_di (v1)); @@ -2011,6 +2012,7 @@ mips_legitimize_tls_address (rtx loc) case TLS_MODEL_LOCAL_EXEC: + emit_insn (gen_blockage ()); if (Pmode == DImode) emit_insn (gen_tls_get_tp_di (v1)); else -- kkojima at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kkojima at gcc dot gnu dot | |org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28126
next prev parent reply other threads:[~2006-06-22 4:16 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-06-21 16:04 [Bug c/28126] New: " anemo at mba dot ocn dot ne dot jp 2006-06-21 16:36 ` [Bug target/28126] " daney at gcc dot gnu dot org 2006-06-22 4:46 ` kkojima at gcc dot gnu dot org [this message] 2006-07-06 16:20 ` anemo at mba dot ocn dot ne dot jp 2006-07-12 16:08 ` drow at gcc dot gnu dot org 2006-07-13 14:42 ` anemo at mba dot ocn dot ne dot jp 2006-07-13 14:58 ` anemo at mba dot ocn dot ne dot jp 2006-07-21 16:34 ` anemo at mba dot ocn dot ne dot jp 2006-07-30 10:56 ` rsandifo at gcc dot gnu dot org 2006-08-03 21:07 ` rsandifo at gcc dot gnu dot org 2006-08-05 15:48 ` anemo at mba dot ocn dot ne dot jp 2008-09-07 17:33 ` daney at gcc dot gnu dot org 2008-09-08 19:49 ` rdsandiford at googlemail 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=20060622041650.25124.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: 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).