From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 110488 invoked by alias); 16 May 2018 17:02:16 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 110466 invoked by uid 89); 16 May 2018 17:02:15 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=H*i:sk:e344f08, Hx-languages-length:899, H*f:sk:e344f08 X-HELO: mail-wr0-f176.google.com Received: from mail-wr0-f176.google.com (HELO mail-wr0-f176.google.com) (209.85.128.176) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 16 May 2018 17:02:14 +0000 Received: by mail-wr0-f176.google.com with SMTP id a12-v6so2209787wrn.13 for ; Wed, 16 May 2018 10:02:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:from:message-id; bh=XjA28Sc+ABKJM/QYaPjnbCKeD6TGRNbDZSeJJ+mcQTY=; b=H/kgnTdUTsK5i98//sZSqO+CeWmMviqN4ZEYLBw/GimNwYKVxWm5ch41VGFi/mgP6M /h31m9hcn8Lp0IhWHrYfld4C3OjY7PFIEAkVDLFC3KEAvw0Yt3N54c46B3d1MqmzM/5U J4uNEOqCg2e4Yek+erpEMfVi3SYL+YXm+/FwPwOKeNkg6tIVwIKAfEZu/n6Ula15f29I 8/0wm0pLEZRqQMonp/Dig/WOlIk0h1z2LPjU6FyJTBnYFfjaVUSeLmbdjcYRxKJj3v/E aKtvbwKXEoJi68m2jrPt/xm7nBf3EhFubn5OXlRjCAwgAgXGGyQOtCBs0YIiYSLQ5VD7 Ggig== X-Gm-Message-State: ALKqPwcHyV7ViF1tWYl3E65b5YBXdVgyGqlL9aFL3a/hzOnvP7++wufQ NtDllAQvmznmZZGgNCc5eiF5VYTh X-Google-Smtp-Source: AB8JxZqmb57NUydJTYaLKvuiLJOKh7q5m+F4YeULFtjKfOrhZcjuxITDlUEi5X+gSVVMcv10xFNk1w== X-Received: by 2002:adf:ac64:: with SMTP id v91-v6mr1431651wrc.80.1526490131907; Wed, 16 May 2018 10:02:11 -0700 (PDT) Received: from [192.168.178.32] (p2E530C99.dip0.t-ipconnect.de. [46.83.12.153]) by smtp.gmail.com with ESMTPSA id y129-v6sm3483687wmg.44.2018.05.16.10.02.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 May 2018 10:02:11 -0700 (PDT) Date: Wed, 16 May 2018 17:02:00 -0000 User-Agent: K-9 Mail for Android In-Reply-To: References: <784b39d2-3e00-5936-1fd5-ee6c8b794efa@codesourcery.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: Vector pointer modes To: Andrew Stubbs ,gcc@gcc.gnu.org From: Richard Biener Message-ID: X-IsSubscribed: yes X-SW-Source: 2018-05/txt/msg00141.txt.bz2 On May 16, 2018 6:35:05 PM GMT+02:00, Andrew Stubbs = wrote: >On 16/05/18 17:24, Richard Biener wrote: >> On May 16, 2018 6:03:35 PM GMT+02:00, Andrew Stubbs > wrote: >>> Is there a new way of dealing with vectors of pointers? >>=20 >> Maybe you can masquerade it behind a large scalar integer mode?... > >We're using V64DImode to represent a vector of 64 64-bit pointers. The=20 >architecture can hold this in a pair of V64SImode registers; it is not=20 >equivalent to 128 consecutive smaller registers, like NEON does. > >We could use plain DImode to get the same effect from print_operand, >but=20 >that then chooses the wrong alternative, or whole wrong insn pattern >and=20 >bad things would happen. > >Or, do you mean something else? I was thinking of using ZImode where hopefully ZI is large enough to hold V= 64DI...=20 Richard.=20 >Andrew