public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	peturr02@ru.is
Subject: Re: libstdc++/10193: Regression: iostreams no longer threadsafe
Date: Mon, 24 Mar 2003 22:06:00 -0000	[thread overview]
Message-ID: <20030324220504.14419.qmail@sources.redhat.com> (raw)

Synopsis: Regression: iostreams no longer threadsafe

State-Changed-From-To: open->feedback
State-Changed-By: ljrittle
State-Changed-When: Mon Mar 24 22:05:03 2003
State-Changed-Why:
    In terms of there being a change in behavior, your observation is correct.  However, we consider the new behavior to be in line with our published guidelines on application requirements to obtain correct thread safety.  In sum, all library objects  which are visibly shared across threads need to have application-level locking to obtain thread safety.
    After reading the discussion on this topic in the library documentation,
    please report your agreement or disagreement with this change.
    FYI, this behavior has been stable since FSF gcc 3.0 was released.
    Another FYI, in this particular case, the primary problem is that we don't know where interleaving of method calls on the global objects should be allowed or disallowed.  Only the application really knows.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10193


             reply	other threads:[~2003-03-24 22:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 22:06 ljrittle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 22:36 Pétur Runólfsson
2003-03-23 19:46 peturr02

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=20030324220504.14419.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=peturr02@ru.is \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).