From: Richard Henderson <rth@twiddle.net>
To: Andreas Jaeger <aj@suse.de>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: Fix warnings in bits/link.h
Date: Sat, 22 Jan 2005 22:19:00 -0000 [thread overview]
Message-ID: <20050122221903.GA10920@twiddle.net> (raw)
In-Reply-To: <m31xcuhqbz.fsf@gromit.moeb>
On Sun, Jan 09, 2005 at 11:03:28AM +0100, Andreas Jaeger wrote:
> +# if __GNUC_PREREQ (4,0)
> +typedef float La_x86_64_xmm __attribute__ ((vector_size (16)));
> +# else
> typedef float La_x86_64_xmm __attribute__ ((__mode__ (__V4SF__)));
> +# endif
If you're going to be namespace-safe, you should use __vector_size__.
r~
prev parent reply other threads:[~2005-01-22 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 10:03 Andreas Jaeger
2005-01-22 22:19 ` Richard Henderson [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=20050122221903.GA10920@twiddle.net \
--to=rth@twiddle.net \
--cc=aj@suse.de \
--cc=libc-hacker@sources.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).