This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Bad code generation on HPPA platform

From: Jeff Law <law at redhat dot com>
To: Steve Ellcey <sje at cup dot hp dot com>
Cc: andrew_pinski at playstation dot sony dot com, dave at hiauly1 dot hia dot nrc dot ca, gcc at gcc dot gnu dot org, bergner at vnet dot ibm dot com
Date: Thu, 08 May 2008 12:48:27 -0600
Subject: Re: Bad code generation on HPPA platform
References: <200805081838.LAA18678@hpsje.cup.hp.com>

Steve Ellcey wrote:


The psuedo for %r8 does have REG_POINTER set and the psuedo for %r19
does not.  I first see REG_POINTER set for ivtmp___1536 (the psuedo for
%r8) in flow.c.138r.loop2_invariant.  This seems interesting because
Peter's patch, that fixes this problem without undoing Andrews patch,
includes a change to loop-invariant.c, though that change should be
preserving REG_POINTER's during optimization not preventing them.

OK. So what is ivtmp__1536 -- is it a pointer or an index? Can you show me the gimple code which declares and uses ivtmp_1536?


Hmmm, fails for 4.3...  Hmmm, does 4.3 have POINTER_PLUS_EXPR?
(search tree.def for POINTER_PLUS_EXPR).

Jeff

Follow-Ups:
- Re: Bad code generation on HPPA platform
  - From: Andrew Pinski

References:
- Re: Bad code generation on HPPA platform
  - From: Steve Ellcey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]