This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
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 12:19:47 -0700
- Subject: Re: Why the V4QImode vector operations are expanded into many SImode at "oplower" pass?
- References: <000301c55bbb$c896dfb0$0201a8c0@uranus>
On Wed, May 18, 2005 at 11:10:42PM +0800, Ling-hua Tseng wrote:
> So I guess that there are some miss-configured in my ports, but I can't
> find it.
Put a breakpoint at tree-complex.c line 962. Examine the conditions
leading up to
if ((GET_MODE_CLASS (compute_mode) == MODE_VECTOR_INT
|| GET_MODE_CLASS (compute_mode) == MODE_VECTOR_FLOAT)
&& op != NULL
&& op->handlers[compute_mode].insn_code != CODE_FOR_nothing)
return;
to find out why the return isn't taken. There aren't really very
many options.
The one that jumps first to my mind is that the "addv4qi3" instruction
pattern doesn't actually exist because you have a typo in the name.
r~