From: Aldy Hernandez <aldyh@redhat.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Brad Lucier <lucier@math.purdue.edu>, GCC Mailinglist <gcc@gcc.gnu.org>
Subject: Re: altivec amusement
Date: Mon, 25 Feb 2002 17:56:00 -0000 [thread overview]
Message-ID: <0659D754-2A49-11D6-B487-000393750C1E@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202250858140.17322-100000@kern.srcf.societies.cam.ac.uk>
> __builtin_types_compatible_p correctly distinguishes. __typeof
> correctly
> acts like sizeof in that the array-to-pointer and function-to-pointer
> conversions do not apply to its argument. (Of course the value that
> ends
what i'm talking about is this:
int x[5];
int *y;
int foo[__builtin_types_compatible_p (__typeof(x), __typeof(y)) == 1 ?
1 : -1];
brad wants the above to compile.
otherwise you can never pass an "int []" when we expect an
"int *" to an altivec macro/"overloaded function".
perhaps __builtin_types_compatible_p should return true for pointers
and array of the same underlying type (?)
> up getting passed to the function does have those conversions applied.)
>
> --
> Joseph S. Myers
> jsm28@cam.ac.uk
>
>
--
Aldy Hernandez E-mail: aldyh@redhat.com
Professional Gypsy Lost in Australia
Red Hat, Inc.
next prev parent reply other threads:[~2002-02-26 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200202250807.g1P87Hw24573@banach.math.purdue.edu>
2002-02-25 1:00 ` Aldy Hernandez
2002-02-25 1:22 ` Joseph S. Myers
2002-02-25 17:56 ` Aldy Hernandez [this message]
2002-02-26 1:32 ` Joseph S. Myers
2002-02-21 21:28 Brad Lucier
2002-02-22 1:33 ` Richard Henderson
2002-02-22 15:53 ` Aldy Hernandez
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=0659D754-2A49-11D6-B487-000393750C1E@redhat.com \
--to=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
--cc=lucier@math.purdue.edu \
/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).