All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ultralinux@vger.kernel.org
Subject: Re: SMP Sparc64 : bug in clone?
Date: Mon, 25 Mar 2002 08:36:20 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-101704568223436@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-101684978515837@msgid-missing>

   From: Erik de Castro Lopo <nospam@mega-nerd.com>
   Date: Mon, 25 Mar 2002 19:35:51 +1100

   On Mon, 25 Mar 2002 00:12:25 -0800 (PST)
   "David S. Miller" <davem@redhat.com> wrote:
   
   > sparc64-linux-gcc is only for kernel building, it is not
   > going to work for userland applications.
   
   I have actually tried both the standard gcc and sparc64-linux-gcc.
   The clone() system call does not work correctly in either case.

Perhaps you should look at how the glibc sources use and invoke
clone() in the linuxthreads sparc-specific code.  That does work.

I haven't looked at your sources because I cannot simply grab it
with wget (which doesn't understand https).  You're probably just
doing something silly.  There are all sorts of platform specific
nuances to do with the stack pointer you pass into clone(), on Sparc
for example the stack you pass in must be at least 8 byte aligned.

  parent reply	other threads:[~2002-03-25  8:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-23  2:15 SMP Sparc64 : bug in clone? Erik de Castro Lopo
2002-03-23  3:33 ` Erik de Castro Lopo
2002-03-25  7:53 ` Erik de Castro Lopo
2002-03-25  8:12 ` David S. Miller
2002-03-25  8:35 ` Erik de Castro Lopo
2002-03-25  8:36 ` David S. Miller [this message]
2002-04-29 20:14 ` David S. Miller
2002-04-29 20:17 ` Erik de Castro Lopo
2002-05-04 23:08 ` Erik de Castro Lopo
2002-05-06 14:25 ` Noah Beck
2002-05-06 21:36 ` Erik de Castro Lopo

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=marc-linux-ultrasparc-101704568223436@msgid-missing \
    --to=davem@redhat.com \
    --cc=ultralinux@vger.kernel.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 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.