From: Daniel Egger <degger@fhm.edu>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: Aldy Hernandez <aldyh@redhat.com>,
GCC Developer Mailinglist <gcc@gcc.gnu.org>
Subject: Re: builtin_types_compatible_p and const
Date: Tue, 26 Feb 2002 05:35:00 -0000 [thread overview]
Message-ID: <1014725857.28077.16.camel@sonja> (raw)
In-Reply-To: <Pine.LNX.4.33.0202260919250.30392-100000@kern.srcf.societies.cam.ac.uk>
Am Die, 2002-02-26 um 10.24 schrieb Joseph S. Myers:
> If vec_lvsl accepts "char *" rather than "const char *", presumably it
> modifies what's pointed to by its argument (else why wasn't it specified
> to use const, unless the interface predates ANSI C89)?
No it doesn't. I simply takes the given address & 0xF and generates
a permutation vector that can be used to align data not aligned
on a 16byte boundary.
On a side note: The AltiVec Programming Interface Manual stats on
side 100:
"d = vec_lvsl (a, b)"
and further
"The b type may also be a pointer to a const- or volatile-qualified
type"
and to backup my complaint about not being able to vec_ld from
const types:
"d = vec_ld (a, b)"
[...]
"The b type may also be a pointer to a const-qualified type"
--
Servus,
Daniel
prev parent reply other threads:[~2002-02-26 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 16:00 AltiVec too pedantic about type qualifiers [UPDATE] Daniel Egger
2002-02-24 18:10 ` Aldy Hernandez
2002-02-25 5:39 ` Daniel Egger
2002-02-25 17:55 ` builtin_types_compatible_p and const Aldy Hernandez
2002-02-25 21:10 ` Daniel Jacobowitz
2002-02-26 1:57 ` Joseph S. Myers
2002-02-26 5:35 ` 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=1014725857.28077.16.camel@sonja \
--to=degger@fhm.edu \
--cc=aldyh@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
/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).