From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: <libc-ports@sourceware.org>, Roland McGrath <roland@hack.frob.com>
Subject: Re: Unused sys/ucontext.h files
Date: Wed, 22 Jan 2014 17:14:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1401221709470.10535@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201401212341.32520.vapier@gentoo.org>
On Tue, 21 Jan 2014, Mike Frysinger wrote:
> On Tuesday 21 January 2014 22:26:54 Joseph S. Myers wrote:
> > I notice that there are files
> >
> > ports/sysdeps/arm/sys/ucontext.h
> > ports/sysdeps/m68k/sys/ucontext.h
> > ports/sysdeps/mips/sys/ucontext.h
> >
> > that are overridden by files in ports/sysdeps/unix/sysv/linux/<arch>, and
> > so unused. Roland, is the ARM file of use for the NaCl port, or should
> > all three of those files be removed?
>
> are we saying that if it's not used by Linux we're just deleting it now ?
No, that if it's not used by any current configuration (which currently
means Hurd or Linux) it's deleted unless it's of use in bringing up a new
port ("generic" files, whether pure stubs or actual generic
implementations). And I strongly suspect these files are just files for
whatever Unix was first supported on a given architecture - I don't really
see advantages of such files over sysdeps/generic/sys/ucontext.h in the
context of bringing up ports (which I expect would inevitably need
OS-specific versions of this file in the end).
(The sysdeps/i386/sys/ucontext.h file is, I suppose, used by Hurd, but
other <arch>/sys/ucontext.h files appear either unused, or in the am33
case maybe really a Linux file in the wrong place.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-01-22 17:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-22 3:27 Joseph S. Myers
2014-01-22 4:41 ` Mike Frysinger
2014-01-22 17:14 ` Joseph S. Myers [this message]
2014-01-22 20:40 ` Thomas Schwinge
2014-01-28 22:43 ` 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=Pine.LNX.4.64.1401221709470.10535@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=vapier@gentoo.org \
/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).