public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xantares09 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/67141] wrong libgomp mutex initialisation order Date: Tue, 11 Aug 2015 17:33:00 -0000 [thread overview] Message-ID: <bug-67141-4-k3v4SXNyzQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67141-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67141 xantares09 at hotmail dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xantares09 at hotmail dot com --- Comment #1 from xantares09 at hotmail dot com --- Created attachment 36169 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36169&action=edit call initialize_env before goacc_host_init I can reproduce here: err:module:attach_process_dlls "libgomp-1.dll" failed to initialize, aborting Mattias is totally right: if i assign a higher initialization priority to env.c:initialize_env than oacc-host.c:goacc_host_init the dll is correctly initialized the patch may not be ok, but you get the idea
next prev parent reply other threads:[~2015-08-11 17:33 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-06 21:47 [Bug libgomp/67141] New: " mattiase at acm dot org 2015-08-11 17:33 ` xantares09 at hotmail dot com [this message] 2015-08-12 8:01 ` [Bug libgomp/67141] " xantares09 at hotmail dot com 2015-08-24 18:42 ` jakub at gcc dot gnu.org 2015-09-11 10:17 ` ktietz at gcc dot gnu.org 2015-09-21 9:36 ` tschwinge at gcc dot gnu.org 2015-09-22 6:46 ` cltang at gcc dot gnu.org 2015-09-22 11:19 ` cltang at gcc dot gnu.org 2015-09-24 13:33 ` cltang at gcc dot gnu.org 2015-10-28 13:31 ` xantares09 at hotmail dot com
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-67141-4-k3v4SXNyzQ@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).