public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: eric.norum@usask.ca To: gcc-gnats@gcc.gnu.org Subject: libstdc++/4367: Sparc atomicity.h routines can lock up on some OS. Date: Thu, 20 Sep 2001 07:56:00 -0000 [thread overview] Message-ID: <20010920145001.19560.qmail@sourceware.cygnus.com> (raw) >Number: 4367 >Category: libstdc++ >Synopsis: Sparc atomicity.h routines can lock up on some OS. >Confidential: no >Severity: serious >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Sep 20 07:56:02 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Eric Norum >Release: gcc-3.0 >Organization: >Environment: Real-time OS environments (e.g. vxWorks, pSOS+, eCOS, RTEMS) >Description: The sparc version of the routines in atomicity.h can lock up on operating systems which provide strict priority-based scheduling (e.g. vxWorks, pSOS+, eCOS, RTEMS). Here's the scenario: 1) Low priority task enters __exchange_and_add and sets the lock. 2) While low-priority task is still active in __exchange_and_add a higher-priority task preempts. 3) The higher-priority task enters __exchange_and_add and enters an infinite loop trying to set the lock. >How-To-Repeat: >Fix: None that I can think of, unfortunately! >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2001-09-20 7:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-09-20 7:56 eric.norum [this message] 2001-09-20 8:26 Phil Edwards 2002-04-01 18:56 bkoz 2002-04-02 0:16 Richard Henderson 2002-04-02 7:36 Eric Norum 2002-04-02 13:56 Richard Henderson 2002-10-01 22:14 davem 2002-11-01 18:05 bkoz 2002-11-02 1:38 davem
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=20010920145001.19560.qmail@sourceware.cygnus.com \ --to=eric.norum@usask.ca \ --cc=gcc-gnats@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).