Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Alan Modra <alan@SPRI.Levels.UniSA.Edu.Au>
Cc: Matthew Wilcox <matthew@wil.cx>,
	John David Anglin <dave@hiauly1.hia.nrc.ca>,
	parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] glibc 2.2.3: setjmp/longjmp
Date: Sat, 5 May 2001 02:01:57 +0100	[thread overview]
Message-ID: <20010505020157.O32445@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.30.0105051006540.7087-100000@mullet.itr.unisa.edu.au>; from alan@SPRI.Levels.UniSA.Edu.Au on Sat, May 05, 2001 at 10:19:05AM +0930

On Sat, May 05, 2001 at 10:19:05AM +0930, Alan Modra wrote:
> Oh horrible.  Yes, the stack frame that sysdeps/generic/bsd-_setjmp.c is
> using to load rp is no longer valid.  Oh well, the comment in
> generic/bsd-_setjmp.c should have warned us,

sure, if we'd ever looked in there :-)

on this subject, there've now been three things (LFS, ELF_OSABI_LINUX
and setjmp) which people have said `oh yeah, thought we might have some
problems with those, someone mentioned that' (or similar) once the problem
was found.  would anyone care to remember anything else that they thought
`might be a problem at some point'?

> which leads to another
> question.  Why was this added to gcc/config/pa/pa-linux.h?
> 
> /* Sibcalls, stubs, and elf sections don't play well.  */
> #undef FUNCTION_OK_FOR_SIBCALL
> #define FUNCTION_OK_FOR_SIBCALL(x) 0
> 
> Seems a bit drastic to me.  The correspnding define in pa.h should be OK
> for us.

I vaguely remember that.  Searching the list archive finds:
http://lists.parisc-linux.org/pipermail/parisc-linux/2000-July/009002.html

so it's dhd's fault :-)

-- 
Revolutions do not require corporate support.

  reply	other threads:[~2001-05-05  1:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-04 20:05 [parisc-linux] glibc 2.2.3: setjmp/longjmp Matthew Wilcox
2001-05-04 20:18 ` John David Anglin
2001-05-04 20:39   ` Matthew Wilcox
2001-05-04 21:02   ` Matthew Wilcox
2001-05-04 21:31     ` John David Anglin
2001-05-04 21:38       ` Matthew Wilcox
2001-05-04 21:51         ` John David Anglin
2001-05-04 22:36           ` Matthew Wilcox
2001-05-04 22:56             ` John David Anglin
2001-05-04 22:57           ` Matthew Wilcox
2001-05-05  0:00             ` Matthew Wilcox
2001-05-05  0:49               ` Alan Modra
2001-05-05  1:01                 ` Matthew Wilcox [this message]
2001-05-05  1:18                   ` Alan Modra
2001-05-05  1:47                     ` Matthew Wilcox
2001-05-06  6:14         ` Ulrich Drepper
2001-05-06  7:07           ` Grant Grundler
2001-05-06 15:53             ` John David Anglin
2001-05-06 22:13           ` Matthew Wilcox

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=20010505020157.O32445@parcelfarce.linux.theplanet.co.uk \
    --to=matthew@wil.cx \
    --cc=alan@SPRI.Levels.UniSA.Edu.Au \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@parisc-linux.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