public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/43494] gcc.c-torture/execute/vector-2.c fails with -fpic/-fPIC
Date: Tue, 20 Jul 2010 13:20:00 -0000	[thread overview]
Message-ID: <20100720132009.19854.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43494-578@http.gcc.gnu.org/bugzilla/>



------- Comment #10 from steven at gcc dot gnu dot org  2010-07-20 13:20 -------
Re. comment 9: Well, the order of *this* store and *this* load is the
difference between the test case failing or passing. So I do not think the
problem is between this load and another store.

Before sched2 (or actually, .mach on ia64):

"vector-2.c.213r.compgotos" (notes, NOPs, bundle markers removed):
;; Function f1 (f1)

   30 r15:DI=r12:DI
   29 r14:DI=r12:DI
   35 [r15:DI++]=r32:DI
   36 [post r15:DI+=0xfffffffffffffffc]=r33:DI
    9 [r15:DI]=r34:SI
   21 r8:DI=[r14:DI++]
   28 r9:DI=[r14:DI]
   18 use r8:TI
   39 {return;use b0:DI;}

After .sched2:
"vector-2.c.215r.mach" (notes, NOPs, bundle markers removed):
   30 r15:DI=r12:DI
   29 r14:DI=r12:DI
   35 [r15:DI++]=r32:DI
   36 [post r15:DI+=0xfffffffffffffffc]=r33:DI
   21 r8:DI=[r14:DI++]
   28 r9:DI=[r14:DI]
    9 [r15:DI]=r34:SI
   18 use r8:TI
   39 {return;use b0:DI;}

Note that the only real change in the scheduling is that insn 9 is moved after
insn 21 and insn 28. insn 9 is the store "[r15:DI]=r34:SI" that later expands
to the st4 instruction.


-- 


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


  parent reply	other threads:[~2010-07-20 13:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-23 17:34 [Bug c/43494] New: " ghazi at gcc dot gnu dot org
2010-03-23 17:37 ` [Bug c/43494] " ghazi at gcc dot gnu dot org
2010-03-23 18:23 ` [Bug rtl-optimization/43494] " pinskia at gcc dot gnu dot org
2010-07-13  9:43 ` steven at gcc dot gnu dot org
2010-07-17 23:28 ` steven at gcc dot gnu dot org
2010-07-18 17:21 ` steven at gcc dot gnu dot org
2010-07-18 17:30 ` steven at gcc dot gnu dot org
2010-07-18 17:40 ` steven at gcc dot gnu dot org
2010-07-18 17:48 ` steven at gcc dot gnu dot org
2010-07-19 19:04 ` steven at gcc dot gnu dot org
2010-07-20  8:25 ` amonakov at gcc dot gnu dot org
2010-07-20 13:20 ` steven at gcc dot gnu dot org [this message]
2010-07-20 13:23 ` steven at gcc dot gnu dot org
2010-07-20 13:57 ` steven at gcc dot gnu dot org
2010-07-20 14:14 ` amonakov at gcc dot gnu dot org
2010-07-20 17:56 ` [Bug rtl-optimization/43494] Overlooked dependency causes wrong scheduling, wrong code steven at gcc dot gnu dot org
2010-07-20 18:08 ` [Bug rtl-optimization/43494] [4.4/4.5/4.6 Regression] " steven at gcc dot gnu dot org
2010-07-21  8:10 ` rguenth at gcc dot gnu dot org
2010-07-21  8:22 ` steven at gcc dot gnu dot org
2010-07-21  8:32 ` amonakov at gcc dot gnu dot org
2010-07-21  9:28 ` steven at gcc dot gnu dot org
2010-07-21  9:33 ` steven at gcc dot gnu dot org
2010-07-21  9:49 ` steven at gcc dot gnu dot org
2010-07-21 10:07 ` amonakov at gcc dot gnu dot org
2010-07-22  8:47 ` rguenth at gcc dot gnu dot org
2010-08-17 13:14 ` bernds at gcc dot gnu dot org
2010-08-18 10:50 ` steven at gcc dot gnu dot org
2010-08-18 14:36 ` bernds at gcc dot gnu dot org
2010-08-18 19:00 ` jakub at gcc dot gnu dot org
2010-08-19 13:39 ` bernds at gcc dot gnu dot org
2010-09-10 23:16 ` aoliva at gcc dot gnu dot org

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=20100720132009.19854.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).