Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Matej Kupljen <matej.kupljen@ultra.si>
To: David Daney <ddaney@avtrex.com>
Cc: crossgcc@sources.redhat.com, linux-mips@linux-mips.org
Subject: Re: MIPS SF toolchain
Date: Mon, 12 Sep 2005 09:33:58 +0200	[thread overview]
Message-ID: <1126510438.9647.8.camel@localhost.localdomain> (raw)
In-Reply-To: <4321A823.8050703@avtrex.com>

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

Hi

> Attached is the portions of my patches to glibc-2.3.3 that contain the 
> setjump/longjump hacks.  There are other things in there as well, so you 
> will have to pick and choose as to which parts you want.

Done that :-)

> I did this more as a proof of concept rather than the definitive answer. 
>   There are still some FP instructions being generated but I have not 
> tracked them down yet.

I did. They were in the sysdeps/mips/fpu_control.h
I tested it with busybox and MPlayer and found no SF ins in the
binaries. I run those binaries on kernel which has no FPU emulator.

Versions:
BINUTILS: 2.16.1
GCC:      3.4.4
GLIBC:    2.3.5

Let me know the results, if someone is going to use this patch.

BR,
Matej

[-- Attachment #2: glibc-2.3.5-mips-sf.patch.bz2 --]
[-- Type: application/x-bzip, Size: 988 bytes --]

      reply	other threads:[~2005-09-12  7:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-07 13:09 MIPS SF toolchain Matej Kupljen
2005-09-07 13:54 ` sjhill
2005-09-07 15:33 ` David Daney
2005-09-08  8:41   ` Matej Kupljen
2005-09-08 11:33     ` Matej Kupljen
2005-09-08 12:22       ` Matej Kupljen
2005-09-08 12:29         ` Ralf Baechle
2005-09-08 13:48         ` Dan Kegel
2005-09-08 15:29         ` David Daney
2005-09-09  6:48           ` Matej Kupljen
2005-09-09 15:20             ` David Daney
2005-09-12  7:33               ` Matej Kupljen [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=1126510438.9647.8.camel@localhost.localdomain \
    --to=matej.kupljen@ultra.si \
    --cc=crossgcc@sources.redhat.com \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.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