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: Neil Booth <neil at daikokuya dot co dot uk>
To: Ling-hua Tseng <uranus at it dot muds dot net>
Cc: Richard Henderson <rth at redhat dot com>, gcc at gcc dot gnu dot org
Date: Thu, 19 May 2005 08:20:30 +0900
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>

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

TARGET_INITIALIZER has already been expanded above, so it's not seen
your macro definition below.

Neil.

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]