| To: | linux-mips@oss.sgi.com |
|---|---|
| Subject: | Re: segfault |
| From: | Jim Paris <jim@jtan.com> |
| Date: | Wed, 5 Sep 2001 17:51:32 -0400 |
| In-reply-to: | <20010905191550.B1054@paradigm.rfc822.org>; from flo@rfc822.org on Wed, Sep 05, 2001 at 07:15:50PM +0200 |
| References: | <20010904235410.A8310@neurosis.mit.edu> <20010905191550.B1054@paradigm.rfc822.org> |
| Reply-to: | jim@jtan.com |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5i |
> Do you have a fix for the sysmips(MIPS_ATOMIC_SET) in there ? Or do > you have the glibc compiled as -mips2 for usage of ll/sc ? Yes, I'm pretty sure that fix is in there. I'm confused by the whole mips1/mips2/mips3 thing -- should I be compiling everything with the same -mipsN, and if so, which one? I have a VR41xx processor. The binaries I'm attempting to run are reported by file(1) as being MIPS 1, while the kernel image is reported as being MIPS 3 (even though most of the kernel Makefiles specify -mips2..?) If I use -mips2 when compiling my userspace binaries, the output files are the same size but different, but file(1) still reports them as MIPS 1 and they still crash in the same way. -jim |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: ret_from_sys_call and signal, Ralf Baechle |
|---|---|
| Next by Date: | Re: segfault, Jim Paris |
| Previous by Thread: | Re: segfault, Maciej W. Rozycki |
| Next by Thread: | Re: segfault, Jim Paris |
| Indexes: | [Date] [Thread] [Top] [All Lists] |