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: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?

From: Richard Henderson <rth at redhat dot com>
To: Ling-hua Tseng <uranus at it dot muds dot net>
Cc: gcc at gcc dot gnu dot org
Date: Wed, 18 May 2005 15:56:27 -0700
Subject: Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
References: <000301c55bbb$c896dfb0$0201a8c0@uranus> <20050518191947.GD7099@redhat.com> <20050518202406.M39277@it.muds.net> <20050518211759.GA7593@redhat.com> <20050518215135.M82151@it.muds.net>

On Thu, May 19, 2005 at 06:02:39AM +0800, Ling-hua Tseng wrote:
> struct gcc_target targetm = TARGET_INITIALIZER;
> ...
> #undef  TARGET_VECTOR_MODE_SUPPORTED_P
> #define TARGET_VECTOR_MODE_SUPPORTED_P  unicore_vector_mode_supported_p

This is your bug.  The TARGET_INITIALIZER needs to come last.


r~

Follow-Ups:
- Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
  - From: Ling-hua Tseng

References:
- Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
  - From: Ling-hua Tseng
- Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
  - From: Richard Henderson
- Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
  - From: Ling-hua Tseng
- Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
  - From: Richard Henderson
- Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
  - From: Ling-hua Tseng

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