public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: David Edelsohn <dje@watson.ibm.com>, gcc@gcc.gnu.org
Subject: Re: generic vectors: how should they work?
Date: Wed, 01 Sep 2004 19:52:00 -0000	[thread overview]
Message-ID: <20040901195245.GA13811@redhat.com> (raw)
In-Reply-To: <4135E82C.60102@gnu.org>

On Wed, Sep 01, 2004 at 05:18:04PM +0200, Paolo Bonzini wrote:
> My answer is "by reference.  When, and if, they will be supported by 
> hardware, there will be an appropriate -mabi= switch that may change 
> this rule."

I would argue that a generic vector should be passed as if it's
a struct containing N elements of the appropriate type.  Which 
is *not* pass-by-reference on many targets.



r~

  parent reply	other threads:[~2004-09-01 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01  0:35 Janis Johnson
2004-09-01  2:11 ` David Edelsohn
2004-09-01  7:11   ` Paolo Bonzini
2004-09-01 14:49     ` David Edelsohn
2004-09-01 15:13       ` Paolo Bonzini
2004-09-01 15:35         ` Giovanni Bajo
2004-09-01 16:00           ` Paolo Bonzini
2004-09-01 19:52         ` Richard Henderson [this message]
2004-09-01 22:08         ` David Edelsohn
2004-09-02 13:04           ` Paolo Bonzini
2004-09-02 14:06             ` David Edelsohn
2004-09-02 14:27               ` Paolo Bonzini
2004-09-02 18:33             ` Janis Johnson
2004-09-01 23:47       ` Janis Johnson
2004-09-02 17:46         ` Janis Johnson
2004-09-01 20:12 ` James E Wilson
2004-09-01 20:40   ` David Edelsohn
2004-09-01 21:22     ` James E Wilson
2004-09-02  1:07   ` Richard Henderson

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=20040901195245.GA13811@redhat.com \
    --to=rth@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=dje@watson.ibm.com \
    --cc=gcc@gcc.gnu.org \
    /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).