From: Roland McGrath <roland@frob.com>
To: Richard Henderson <rth@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: alpha div/rem and PAL/gentrap constants
Date: Tue, 04 Jun 2002 12:39:00 -0000 [thread overview]
Message-ID: <20020604193932.4FA181BA15@perdition.linnaean.org> (raw)
In-Reply-To: Richard Henderson's message of Tue, 4 June 2002 12:26:35 -0700 <20020604122635.A14573@redhat.com>
> On Tue, Jun 04, 2002 at 02:56:13PM -0400, Roland McGrath wrote:
> > The files sysdeps/alpha/ldiv.S, sysdeps/alpha/div.S, sysdeps/alpha/divrem.h
> > use this and expect it to define the macros PAL_gentrap and GEN_INTDIV:
> >
> > #ifdef __linux__
> > # include <asm/gentrap.h>
> > # include <asm/pal.h>
> > #else
> > # include <machine/pal.h>
> > #endif
>
> Heh. This won't compile on OSF/1 either -- machine/pal.h contains
> only the PAL_code constants. There's a machine/gentrap.h that contains
> (modulo comments) exactly what's in the linux asm/gentrap.h.
That sounds reasonable.
> > Any opinions on which changes or new headers would be best to get libc to
> > compile for non-Linux on Alpha?
>
> I think it'd be nicer to add machine/gentrap.h for Hurd...
I can do that.
next parent reply other threads:[~2002-06-04 19:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020604122635.A14573@redhat.com>
2002-06-04 12:39 ` Roland McGrath [this message]
2002-06-04 11:56 Roland McGrath
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=20020604193932.4FA181BA15@perdition.linnaean.org \
--to=roland@frob.com \
--cc=libc-hacker@sources.redhat.com \
--cc=rth@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).