From: Ulrich Drepper <drepper@redhat.com>
To: Kaz Kojima <kkojima@rr.iij4u.or.jp>
Cc: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] check_pf.c: Include alloca.h
Date: Fri, 06 Jul 2007 22:23:00 -0000 [thread overview]
Message-ID: <468EC0D1.5050104@redhat.com> (raw)
In-Reply-To: <20070707.065436.35682509.kkojima@rr.iij4u.or.jp>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Kaz Kojima wrote:
> Although this is not a problem on x86 because
> alloca.h is included indirectly on that architecture, it looks
> that other users of alloca function include alloca.h explicitly.
I've said several times that I want those differences in the headers to
be eliminated instead. x86 and x86-64 set the standard and all other
archs have to include the same headers.
- --
⧠Ulrich Drepper ⧠Red Hat, Inc. ⧠444 Castro St ⧠Mountain View, CA â
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFGjsDR2ijCOnn/RHQRAomQAKCqNrgB8PRRkw8+90VaFj22eQyk3ACgk7Pf
/bLTX8w/4hOJYvkBicnqWk0=
=IGam
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-07-06 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 21:55 Kaz Kojima
2007-07-06 22:23 ` Ulrich Drepper [this message]
2007-07-06 22:43 ` Kaz Kojima
2007-07-06 23:54 ` Ulrich Drepper
2007-07-07 0:10 ` Kaz Kojima
2007-07-07 1:54 ` Ulrich Drepper
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=468EC0D1.5050104@redhat.com \
--to=drepper@redhat.com \
--cc=kkojima@rr.iij4u.or.jp \
--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).