public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/53785] coalescing multiple static instances in function scope
Date: Wed, 27 Jun 2012 06:59:00 -0000	[thread overview]
Message-ID: <bug-53785-4-GDlbXioB5V@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53785-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53785

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-06-27 06:59:08 UTC ---
The question comes, do we want to have a lock for each variable or one for the
scope?  One for each variable was easier to implement and might be more
correct.  What happens if getId has weird side effects depending on which
thread calls it?


  reply	other threads:[~2012-06-27  6:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-27  6:49 [Bug rtl-optimization/53785] New: " vincenzo.innocente at cern dot ch
2012-06-27  6:59 ` pinskia at gcc dot gnu.org [this message]
2012-06-28  4:43 ` [Bug rtl-optimization/53785] " vincenzo.innocente at cern dot ch
2024-03-17  0:02 ` [Bug c++/53785] " pinskia at gcc dot gnu.org
2024-03-17  0:03 ` pinskia at gcc dot gnu.org

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=bug-53785-4-GDlbXioB5V@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: 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).