mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Alexey Neyman <stilor@att.net>
To: musl@lists.openwall.com
Subject: Re: Providing <sgidefs.h> for MIPS?
Date: Sat, 4 Feb 2017 12:49:21 -0800	[thread overview]
Message-ID: <55f37695-3418-f806-c95b-b30fde2246d7@att.net> (raw)
In-Reply-To: <52a24746-2e25-9e4d-0b52-9ba026417ef4@att.net>

[Sorry for not CC'ing, Richard Felker - I am not subscribed to this 
list, so I only saw your response on the website as you only replied to 
the list]

Relaying one more response from GDB maintainers:

[[[[

  NB the published API set out by SGI is actually <sys/asm.h> [1][2][3]
rather than <sgidefs.h>, so if musl does the right thing via the former
header then I'll be happy to accept a patch to switch.  Otherwise I'll be
closing the bug as invalid.

References:

[1] "MIPSpro Compiling and Performance Tuning Guide", Silicon Graphics,
     Inc., Document Number 007-2360-008, Section 6.3.2 "Using Predefined
     Types", p. 135
<http://techpubs.sgi.com/library/manuals/2000/007-2360-008/pdf/007-2360-008.pdf>

[2] "MIPSpro 64-Bit Porting and Transition Guide", Silicon Graphics, Inc.,
     Document Number 007-2391-006, Section "Using a Different Subrouting
     Linkage", p. 45
<http://techpubs.sgi.com/library/manuals/2000/007-2391-006/pdf/007-2391-006.pdf>

[3] "MIPSpro N32 ABI Handbook", Silicon Graphics, Inc., Document Number
     007-2816-004, Section "Using a Different Subroutine Linkage", p. 22
<http://techpubs.sgi.com/library/manuals/2000/007-2816-004/pdf/007-2816-004.pdf>

]]]]

I don't have a particular stake in this game, but if it is a de-facto 
standard for MIPS, musl might want to adhere to it.

Regards,
Alexey.


On 01/25/2017 11:31 PM, Alexey Neyman wrote:
> Hi,
>
> In crosstool-ng, a failure to build native GDB for mips-*-mips has 
> been reported: https://github.com/crosstool-ng/crosstool-ng/pull/517
>
> The reason is a missing <sgidefs.h> header (which is provided by 
> glibc/uClibc, but not by musl). The reporter suggested to use 
> <asm/sgidefs.h> from the Linux kernel instead. However, GDB developers 
> seem to disagree: 
> https://sourceware.org/ml/gdb-patches/2017-01/msg00446.html; their 
> view is that the <sgidefs.h> header is to be provided as a part of the 
> user-space headers.
>
> Should musl provide one?
>
> Regards,
> Alexey.
>



      parent reply	other threads:[~2017-02-04 20:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  7:31 Alexey Neyman
2017-01-26 14:53 ` Rich Felker
2017-02-04 20:49 ` Alexey Neyman [this message]

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=55f37695-3418-f806-c95b-b30fde2246d7@att.net \
    --to=stilor@att.net \
    --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).