public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/60078] acats c761007 fails on ARM Date: Sun, 04 Jan 2015 17:42:00 -0000 [thread overview] Message-ID: <bug-60078-4-zq5ips698R@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60078-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60078 --- Comment #15 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > that happened only once. and the problem did never ever repeat. > But my gut feeling is still that there is a race conditition. Yes, I agree that the usage of Side_Effect_Finger looks suspicious here. > However I have been recently working on TSAN a bit, and I have an > experimental tsan version that I played with. Initially > it ICE'd on Ada's VIEW_CONVERT_EXPRs, but when I fixed that I got: "data races" (unprotected concurrent accesses) are allowed in Ada if the object is declared as atomic, in which case GNAT generates synchronization directives.
prev parent reply other threads:[~2015-01-04 17:42 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-05 14:47 [Bug ada/60078] New: " bernd.edlinger at hotmail dot de 2014-02-05 18:26 ` [Bug ada/60078] " mikpelinux at gmail dot com 2014-02-05 18:43 ` ebotcazou at gcc dot gnu.org 2014-02-05 19:52 ` mikpelinux at gmail dot com 2014-02-06 9:08 ` bernd.edlinger at hotmail dot de 2014-02-06 11:37 ` ebotcazou at gcc dot gnu.org [not found] ` <bug-60078-4-vWURbZQ2ze@http.gcc.gnu.org/bugzilla/> 2014-02-06 13:24 ` Arnaud Charlet 2014-02-06 13:25 ` charlet at adacore dot com 2014-02-06 13:40 ` bernd.edlinger at hotmail dot de 2014-02-06 13:46 ` Arnaud Charlet 2014-02-06 13:46 ` charlet at adacore dot com 2014-02-06 14:03 ` bernd.edlinger at hotmail dot de 2015-01-01 14:41 ` bernd.edlinger at hotmail dot de 2015-01-04 17:42 ` ebotcazou at gcc dot gnu.org [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=bug-60078-4-zq5ips698R@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: 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).