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: Thu, 08 Sep 2005 14:22:02 +0200	[thread overview]
Message-ID: <1126182122.25393.27.camel@orionlinux.starfleet.com> (raw)
In-Reply-To: <1126179199.25389.20.camel@orionlinux.starfleet.com>

Hi

I think I found the problem.

> -------------------------------------------------------------
> 0002fe80 <__longjmp>:
>    2fe80:       c4940038        lwc1    $f20,56(a0)
>    2fe84:       c495003c        lwc1    $f21,60(a0)
....

This code is written in  sysdeps/mips/setjmp_aux.c in 
inline assembly.

> and
> -------------------------------------------------------------
> 0002ff70 <__sigsetjmp_aux>:
>    2ff70:       3c1c0017        lui     gp,0x17
>    2ff74:       279cce40        addiu   gp,gp,-12736

This code is written in sysdeps/mips/__longjmp.c in 
inline assembly.

> How to solve this?

Because I am using sf, there is no need to store those
registers, or is it?
Can I just #ifdef this code if compiled for sf?

BR,
Matej

  reply	other threads:[~2005-09-08 12:15 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 [this message]
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

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=1126182122.25393.27.camel@orionlinux.starfleet.com \
    --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