public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/99529] libgfortran I/O: Data races related to new unit / new unit calls for I/O to strings Date: Thu, 11 Mar 2021 09:48:34 +0000 [thread overview] Message-ID: <bug-99529-4-8FqoB7L6IR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99529-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99529 --- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> --- Patch: https://gcc.gnu.org/pipermail/gcc-patches/2021-March/566596.html @Martin: Besides helgrind, you could also try building your program with -fsanitize=thread - this might also help finding some issues (for environment flags, see https://github.com/google/sanitizers/wiki/ThreadSanitizerFlags )
next prev parent reply other threads:[~2021-03-11 9:48 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 21:10 [Bug fortran/99529] New: " burnus at gcc dot gnu.org 2021-03-10 21:30 ` [Bug fortran/99529] " burnus at gcc dot gnu.org 2021-03-11 8:30 ` rguenth at gcc dot gnu.org 2021-03-11 8:52 ` mscfd at gmx dot net 2021-03-11 9:07 ` mscfd at gmx dot net 2021-03-11 9:31 ` burnus at gcc dot gnu.org 2021-03-11 9:48 ` burnus at gcc dot gnu.org [this message] 2021-03-15 13:29 ` burnus 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-99529-4-8FqoB7L6IR@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).