mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: stable 1.1.9 & current GIT broken on mips
Date: Tue, 2 Jun 2015 19:52:15 +0200	[thread overview]
Message-ID: <556DED4F.5040000@dd-wrt.com> (raw)
In-Reply-To: <20150602171924.GI17573@brightrain.aerifal.cx>

Am 02.06.2015 um 19:19 schrieb Rich Felker:
> On Tue, Jun 02, 2015 at 05:57:23PM +0200, Sebastian Gottschall wrote:
>> Hello
>>
>> i tested today the current 1.1.9 (and later also current git so see
>> if its the same behaviour)
>> build on a mipsr2 big endian target (atheros ar7xxx) based on my
>> dd-wrt firmware.
>> i found out that mips seems to be broken on musl right now. the
>> behaviour is
>> that a call using execvp will not result in calling the desired
>> application.
>> on a second call and a following return call, the userspace will
>> lock up with no way todo anything anymore.
>>
>> for testing i used the same compiler, just recompiled musl with
>> version 1.1.8 and overwrote the libc library and crt stuff. the
>> result was, that it worked
>> again without any issue
>>
>> it needs to be considered that parts of the code is compiled using
>> -mips16 and -minterlink-mips16 if that matters
> I suspect the regression is related to your use of mips16, which I had
> no idea worked at all with musl and is not something that's officially
> supported. Did you build musl itself as mips16? I don't think this is
> going to work because we have tail calls back and forth between C and
> asm code where the asm is written in normal 32-bit mips instructions.
> There may also be issues with the dynamic linker start code if
> crt_arch.h is assembled in mips16 mode.
no musl itself is build without mips16. i'm aware that this will likelly 
not work. only the applications are partially compiled with mips16 (some 
libs like openssl arent compiled with mips16 for performance reasons)
> Could you provide details on your setup, specifically, which
> components are being compiled as mips16?
all libs and applications which are affected here in this testcase are 
compiled with mips16, except for musl

Sebastian
>
> Rich
>



  reply	other threads:[~2015-06-02 17:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02  9:09 time.h define NULL Tomasz Sterna
2015-06-02  9:35 ` Szabolcs Nagy
2015-06-02  9:38   ` Daniel Cegiełka
2015-06-02  9:41     ` Szabolcs Nagy
2015-06-02 11:16   ` Tomasz Sterna
2015-06-02 11:24     ` Szabolcs Nagy
2015-06-02 12:04       ` Tomasz Sterna
2015-06-02 15:57         ` stable 1.1.9 & current GIT broken on mips Sebastian Gottschall
2015-06-02 17:19           ` Rich Felker
2015-06-02 17:52             ` Sebastian Gottschall [this message]
2015-06-02 19:11               ` Rich Felker
2015-06-02 19:59                 ` Sebastian Gottschall
2015-06-04  4:04                   ` Rich Felker
2015-06-04  8:29                     ` Sebastian Gottschall
2015-06-04 12:14                     ` Sebastian Gottschall
2015-06-04 16:07                       ` Rich Felker
2015-06-06 15:42                         ` Anthony G. Basile
2015-06-06 15:59                           ` Anthony G. Basile
2015-06-02 11:32     ` time.h define NULL Jens Gustedt

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=556DED4F.5040000@dd-wrt.com \
    --to=s.gottschall@dd-wrt.com \
    --cc=dalias@libc.org \
    --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).