From: Khem Raj <raj.khem@gmail.com>
To: musl@lists.openwall.com
Subject: Re: [musl] remove SIGSTKFLT on mips?
Date: Thu, 21 May 2020 13:20:50 -0700 [thread overview]
Message-ID: <2bd98ffc-f82f-a11d-b14a-15226f1ebf4a@gmail.com> (raw)
In-Reply-To: <20200521192102.GF1079@brightrain.aerifal.cx>
On 5/21/20 12:21 PM, Rich Felker wrote:
> On Thu, May 21, 2020 at 09:51:29AM -0700, enh wrote:
>> (context: https://github.com/landley/toybox/issues/194)
>>
>> seems like musl defines SIGSTKFLT for mips as signal 7. the kernel
>> disagrees and says SIGEMT is 7, and that mips doesn't have a
>> SIGSTKFLT:
>>
>> arch/mips/include/uapi/asm/signal.h:#define SIGEMT 7
>>
>> git blame says SIGSTKFLT was introduced in the original commit:
>>
>> commit 6315004f6102dca44c4ba50654a36967b8b9c2a6
>> Author: Rich Felker <dalias@aerifal.cx>
>> Date: Wed Jul 11 04:22:13 2012 -0400
>>
>> initial version of mips (o32) port, based on work by Richard
>> Pennington (rdp)
>>
>> basically, this version of the code was obtained by starting with
>> rdp's work from his ellcc source tree, adapting it to musl's build
>> system and coding style, auditing the bits headers for discrepencies
>> with kernel definitions or glibc/LSB ABI or large file issues, fixing
>> up incompatibility with the old binutils from aboriginal linux, and
>> adding some new special cases to deal with the oddities of sigaction
>> and pipe syscall interfaces on mips.
>>
>> at present, minimal test programs work, but some interfaces are broken
>> or missing. threaded programs probably will not link.
>
> I have the two attached patches pending push if there's no objection.
>
seems good to me
> Rich
>
next prev parent reply other threads:[~2020-05-21 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 16:51 enh
2020-05-21 19:21 ` Rich Felker
2020-05-21 20:20 ` Khem Raj [this message]
2020-05-21 20:23 ` Rich Felker
2020-05-23 15:46 ` Petr Vorel
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=2bd98ffc-f82f-a11d-b14a-15226f1ebf4a@gmail.com \
--to=raj.khem@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).