public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/65458] parloops transforms omp-thread functions Date: Wed, 18 Mar 2015 11:28:00 -0000 [thread overview] Message-ID: <bug-65458-4-eXsLtN6bFh@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65458-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65458 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-03-18 Ever confirmed|0 |1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Agreed.
next prev parent reply other threads:[~2015-03-18 11:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-18 7:45 [Bug tree-optimization/65458] New: parloops transforms omp-generated functions vries at gcc dot gnu.org 2015-03-18 11:28 ` rguenth at gcc dot gnu.org [this message] 2015-03-19 7:27 ` [Bug tree-optimization/65458] parloops transforms omp-thread functions vries at gcc dot gnu.org 2015-03-21 12:55 ` vries at gcc dot gnu.org 2015-03-21 13:02 ` vries at gcc dot gnu.org 2015-03-22 8:53 ` vries 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-65458-4-eXsLtN6bFh@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).