public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@godzilla.ics.uci.edu>
To: "Sanjiv Kumar Gupta, Noida" <sanjivg@noida.hcltech.com>
Cc: Daniel Berlin <dberlin@dberlin.org>,
	Dale Johannesen <dalej@apple.com>,
	gcc@gcc.gnu.org
Subject: Re: possible gcse failure: not able to eliminate redundant loads
Date: Thu, 12 Dec 2002 21:44:00 -0000	[thread overview]
Message-ID: <200212130641.gBD6fcU20260@amrm2.ics.uci.edu> (raw)
In-Reply-To: <E04CF3F88ACBD5119EFE00508BBB2121061C2FC5@exch-01.noida.hcltech.com>

"Sanjiv Kumar Gupta, Noida" <sanjivg@noida.hcltech.com> writes:

  >  
  > >> We have the code for it, but alias.c isn't helping.
  > 
  > >It looks like memrefs_conflict_p is supposed to be able to prove that
  > a[2] and a[4] don't alias, I wonder why it's not working?
  > 
  > It can detect different offsets in 'reg+offset' forms of addresses
  > but can not distinguish between two pointer regs. 
  > In this case, the machine (sh4) doesn't support reg+offset addressing
  > for double-precision values.
  > I am working on memrefs_conflict_p to handle this.

It works just fine on SPARC, so it might be something specific to your
port... 

        ldd     [%o0+8], %f8
        cmp     %o2, 2  !  i
        bg      .LL8
        std     %f8, [%o1+16]
        add     %o2, 8, %o2     !  i,  i
.LL10:
        cmp     %o2, 2  !  i
        ble,a   .LL10
        add     %o2, 8, %o2     !  i,  i
        std     %f8, [%o0+32]
.LL8:
        nop
        retl
        nop


  reply	other threads:[~2002-12-13  5:35 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-12 21:35 Sanjiv Kumar Gupta, Noida
2002-12-12 21:44 ` Dan Nicolaescu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-21 20:36 Robert Dewar
2002-12-19  7:08 Richard Kenner
2002-12-18 18:39 Robert Dewar
2002-12-19  3:02 ` Richard Henderson
2002-12-21 19:49 ` Alexandre Oliva
2002-12-13  0:39 Sanjiv Kumar Gupta, Noida
2002-12-13  2:42 ` Richard Henderson
2002-12-13 13:10   ` Toon Moene
2002-12-16 10:15     ` Richard Henderson
2002-12-16 11:32       ` Andrew Haley
2002-12-16 13:13       ` Toon Moene
2002-12-16 13:32         ` Richard Henderson
2002-12-16 14:44           ` Toon Moene
2002-12-16 14:48             ` Toon Moene
2002-12-16 15:29               ` Richard Henderson
2002-12-17 15:20                 ` Toon Moene
2002-12-16 15:38               ` Jan Hubicka
2002-12-16 16:40           ` Alex Rosenberg
2002-12-12 23:42 Sanjiv Kumar Gupta, Noida
2002-12-11 22:00 Sanjiv Kumar Gupta, Noida
2002-12-11 22:18 ` Daniel Berlin
2002-12-11 20:32 Sanjiv Kumar Gupta, Noida
2002-12-11  3:30 Sanjiv Kumar Gupta, Noida
2002-12-11 14:53 ` Dale Johannesen
2002-12-11 20:02   ` Daniel Berlin
2002-12-11 20:03     ` Daniel Berlin
2002-12-12 12:25     ` Richard Henderson
2002-12-12 12:28       ` Daniel Berlin
2002-12-12 13:03         ` Richard Henderson
2002-12-12 13:04           ` David Edelsohn
2002-12-12 14:32             ` Richard Henderson
2002-12-12 14:42               ` David Edelsohn
2002-12-12 14:58                 ` Richard Henderson
2002-12-12 15:28                   ` Daniel Berlin
2002-12-13  3:41                     ` Richard Henderson
2002-12-12 20:30                   ` David Edelsohn
2002-12-12 15:29               ` Geoff Keating
2002-12-11  3:27 Sanjiv Kumar Gupta, Noida

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=200212130641.gBD6fcU20260@amrm2.ics.uci.edu \
    --to=dann@godzilla.ics.uci.edu \
    --cc=dalej@apple.com \
    --cc=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=sanjivg@noida.hcltech.com \
    /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).