public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "daniel.f.starke at freenet dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/48659] Segmentation fault when using openMP and SSE Date: Mon, 28 Jan 2013 11:53:00 -0000 [thread overview] Message-ID: <bug-48659-4-otusvk7eiV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48659-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48659 --- Comment #3 from Daniel Starke <daniel.f.starke at freenet dot de> 2013-01-28 11:53:14 UTC --- I can confirm this bug for gcc 4.7.2 mingw64. The -mstackrealign command-line flag can be used as workaround as described on http://stackoverflow.com/questions/6716654/segmentation-fault-using-openmp-and-sse until this bug is properly patched.
prev parent reply other threads:[~2013-01-28 11:53 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-18 6:59 [Bug c++/48659] New: " npozar at quick dot cz 2011-04-18 12:22 ` [Bug c++/48659] " rguenth at gcc dot gnu.org 2013-01-26 14:04 ` [Bug target/48659] " redi at gcc dot gnu.org 2013-01-28 11:53 ` daniel.f.starke at freenet dot de [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-48659-4-otusvk7eiV@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).