All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Matej Kupljen <matej.kupljen@ultra.si>
Cc: David Daney <ddaney@avtrex.com>,
	crossgcc@sources.redhat.com, linux-mips@linux-mips.org
Subject: Re: MIPS SF toolchain
Date: Thu, 08 Sep 2005 06:48:19 -0700	[thread overview]
Message-ID: <43204123.8000204@kegel.com> (raw)
In-Reply-To: <1126182122.25393.27.camel@orionlinux.starfleet.com>

Matej Kupljen wrote:
> I think I found the problem.
> 
> ....
> 
> This code is written in  sysdeps/mips/setjmp_aux.c in 
> inline assembly.  ...
> 
> This code is written in sysdeps/mips/__longjmp.c in 
> inline assembly.
> 
> 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?

Other architectures do things like this, e.g.

sysdeps/powerpc/powerpc32/__longjmp-common.S:#ifdef __NO_VMX__

so I don't see why not.

In fact, I had to do something similar once to make life
possible for ppc405.  See

http://kegel.com/xgcc3/glibc-ppc-nofpu.patch3

(Hmm, wonder if something like that ever made it in to
mainline glibc.)

- Dan

-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html

  parent reply	other threads:[~2005-09-08 13:55 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 [this message]
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=43204123.8000204@kegel.com \
    --to=dank@kegel.com \
    --cc=crossgcc@sources.redhat.com \
    --cc=ddaney@avtrex.com \
    --cc=linux-mips@linux-mips.org \
    --cc=matej.kupljen@ultra.si \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.