From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14748 invoked by alias); 24 Jul 2002 18:01:15 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 14624 invoked from network); 24 Jul 2002 18:01:06 -0000 Received: from unknown (HELO atlrel8.hp.com) (156.153.255.206) by sources.redhat.com with SMTP; 24 Jul 2002 18:01:06 -0000 Received: from hpda.cup.hp.com (cup.hp.com [15.75.208.53]) by atlrel8.hp.com (Postfix) with ESMTP id 23BF3A00088; Wed, 24 Jul 2002 14:01:06 -0400 (EDT) Received: from hpsje.cup.hp.com (hpsje.cup.hp.com [15.244.96.221]) by hpda.cup.hp.com (Postfix) with ESMTP id 5AC90A1EC; Wed, 24 Jul 2002 11:01:05 -0700 (PDT) Received: (from sje@localhost) by hpsje.cup.hp.com (8.8.6 (PHNE_17190)/8.7.3 TIS Messaging 5.0) id LAA22452; Wed, 24 Jul 2002 11:01:05 -0700 (PDT) Date: Wed, 24 Jul 2002 15:22:00 -0000 From: Steve Ellcey Message-Id: <200207241801.LAA22452@hpsje.cup.hp.com> To: gcc@gcc.gnu.org Subject: Re: Vector modes under hppa64-hpu Cc: aldyh@redhat.com, dave@hiauly1.hia.nrc.ca Reply-To: sje@cup.hp.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-07/txt/msg01169.txt.bz2 Well, following up to my own mail, I have a couple of questions. If I am on a system that does not support the VECTOR modes, should I ever see any rtx with a type of V2SImode? I don't think I should, but I am not sure. When I run simd-1.c with -O0 on IA64 or PA64 I never see any code with this mode. When I run with -O1 I do see such code. I believe that this code is coming from store_constructor in expr.c. With -O1, when "TREE_CODE (type) == VECTOR_TYPE" I wind up setting need_to_clear to 1 because I am storing into a (64 bit) register, and that in turn winds up calling emit_move_insn with a mode of V2SImode and I think that is wrong since my platform does not support V2SImode. With -O0, I do not store into a register so store_constructor doesn't set need_to_clear and everything works OK. Steve Ellcey sje@cup.hp.com