public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] linuxthread stack problem
Date: Mon, 04 Nov 2002 23:03:48 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805331@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805328@msgid-missing>

>>>>> On Mon, 04 Nov 2002 12:43:46 -0600, Philip Armstrong <pma@sgi.com> said:

  Philip> While in the same subroutine, however, the ordering of the
  Philip> pthread_cleanup_buffer stack addresses as allocated by the
  Philip> pthread_cleanup_push macro is indeterminate, at least it is
  Philip> on our IA64 platform.

  Philip> I have simplified the problem into a short test case that
  Philip> uses the bracketing and stack address allocation in the same
  Philip> manner that the pthread_cleanup_push() and
  Philip> pthread_cleanup_pop() macros do. In my case, we have
  Philip> STACK_GROW_DOWN defined, and as you can see the second stack
  Philip> address is actually greater than the first. The
  Philip> pthread_cancel routine would not execute the second cleanup
  Philip> subroutine put on the stack in this case becuase the address
  Philip> comparison (FRAME_LEFT in linuxthreads/cancel.c) would
  Philip> prohibit it.

You also might want to send this question to one of the gcc mailing
lists.

	--david


      parent reply	other threads:[~2002-11-04 23:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 18:43 [Linux-ia64] linuxthread stack problem Philip Armstrong
2002-11-04 21:07 ` Mario Smarduch
2002-11-04 23:03 ` David Mosberger [this message]

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-ia64-105590709805331@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox