From: Richard Henderson <rth@twiddle.net>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Andreas Schwab <schwab@suse.de>,
libc-hacker@sources.redhat.com
Subject: Re: Fix ia64/sys/ucontext.h für g++ 3.5
Date: Sat, 04 Sep 2004 01:58:00 -0000 [thread overview]
Message-ID: <20040904015841.GB31433@twiddle.net> (raw)
In-Reply-To: <20040901185338.GL30497@sunsite.ms.mff.cuni.cz>
On Wed, Sep 01, 2004 at 08:53:38PM +0200, Jakub Jelinek wrote:
> Can't it just use the hardcoded value (0xc8 or what was it) and
> do a glibc compile time check somewhere that it is the correct value?
That does seem the best solution.
If you can't use offsetof, then eventually this code will break in C,
with -pedantic, as soon as Joseph Myers gets around to fixing the
parser wrt integer constant expressions.
r~
next prev parent reply other threads:[~2004-09-04 1:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 9:32 Andreas Schwab
2004-09-01 17:25 ` Richard Henderson
2004-09-01 20:56 ` Andreas Schwab
2004-09-01 21:07 ` Ulrich Drepper
2004-09-01 21:11 ` Jakub Jelinek
2004-09-04 1:58 ` Richard Henderson [this message]
2004-09-02 3:40 ` 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=20040904015841.GB31433@twiddle.net \
--to=rth@twiddle.net \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=schwab@suse.de \
/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).