public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daney 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: Wed, 21 Jun 2006 16:36:00 -0000	[thread overview]
Message-ID: <20060621163305.5490.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28126-12556@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from daney at gcc dot gnu dot org  2006-06-21 16:33 -------
Confirmed on: mipsel-linux-gcc (GCC) 4.2.0 20060605 (experimental)
cross compiler configured as:
../gcc/configure   --target=mipsel-linux
--with-sysroot=/usr/local/mipsel-linux-test
--prefix=/usr/local/mipsel-linux-test --with-arch=mips32 --with-float=soft
--disable-libmudflap --enable-tls --enable-languages=c

I get a slightly different output for the test case but the rdhwr is still
being hoisted out of the conditional:

        .file   1 "tls.c"
        .section .mdebug.abi32
        .previous
        .abicalls
        .text
        .align  2
        .globl  foo
        .ent    foo
        .type   foo, @function
foo:
        .frame  $sp,0,$31               # vars= 0, regs= 0/0, args= 0, gp= 0
        .mask   0x00000000,0
        .fmask  0x00000000,0
        .set    noreorder
        .cpload $25
        .set    nomacro

        lw      $2,%gottprel(x)($28)
        .set    push
        .set    mips32r2
        rdhwr   $3,$29
        .set    pop
        beq     $4,$0,$L7
        addu    $2,$2,$3

        j       $31
        lw      $2,0($2)

$L7:
        j       $31
        move    $2,$0

        .set    macro
        .set    reorder
        .end    foo
        .ident  "GCC: (GNU) 4.2.0 20060605 (experimental)"


-- 

daney at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daney at gcc dot gnu dot org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-06-21 16:33:02
               date|                            |


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


  reply	other threads:[~2006-06-21 16:33 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 ` daney at gcc dot gnu dot org [this message]
2006-06-22  4:46 ` [Bug target/28126] " kkojima at gcc dot gnu dot org
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=20060621163305.5490.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: 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).