public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Egger <degger@fhm.edu>
To: Jakub Jelinek <jakub@redhat.com>
Cc: GCC Developer Mailinglist <gcc@gcc.gnu.org>,
	Aldy Hernandez <aldyh@redhat.com>
Subject: Re: Altivec strangeness?
Date: Mon, 25 Feb 2002 07:17:00 -0000	[thread overview]
Message-ID: <1014644865.4393.13.camel@sonja> (raw)
In-Reply-To: <20020225104959.I2204@sunsite.ms.mff.cuni.cz>

Am Mon, 2002-02-25 um 10.49 schrieb Jakub Jelinek:

> If you just want to save typing, with recent Aldy's patch: 
> static const vector signed short foo = { [0 ... 7] = 1 };

Sounds good to me. It's much better to hack and easier to read.
 
> should work (but you have to know how many elements it has, and it
> is a GNU extension).

That's not an issue because
a) I do know the number of elements
b) Code using the gcc altivec extension can be compiled only with gcc
   except for the complete bogus Motorola gcc.

> The result will be the same as { 1, 1, 1, 1, 1, 1, 1, 1 } though,
> so it will load the constant from memory as well.

For now it's okay, needs to be fixed sooner or later though.
 
-- 
Servus,
       Daniel

      reply	other threads:[~2002-02-25 13:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-22  8:25 Daniel Egger
2002-02-22 14:36 ` Aldy Hernandez
2002-02-23 16:50   ` Daniel Egger
2002-02-24 16:00     ` Aldy Hernandez
2002-02-24 16:41       ` Daniel Egger
2002-02-24 18:16         ` Aldy Hernandez
2002-02-25  9:11           ` Daniel Egger
2002-02-25 18:46             ` Aldy Hernandez
2002-02-25  1:59 ` Jakub Jelinek
2002-02-25  7:17   ` Daniel Egger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1014644865.4393.13.camel@sonja \
    --to=degger@fhm.edu \
    --cc=aldyh@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).