public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/67476] Add --param parloops-schedule=<static|dynamic|guided|auto|runtime>
Date: Tue, 13 Oct 2015 10:09:00 -0000 [thread overview]
Message-ID: <bug-67476-4-FgXCJRMiUF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67476-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67476
--- Comment #12 from vries at gcc dot gnu.org ---
Author: vries
Date: Tue Oct 13 10:08:59 2015
New Revision: 228756
URL: https://gcc.gnu.org/viewcvs?rev=228756&root=gcc&view=rev
Log:
Add param parloops-schedule
2015-10-13 Tom de Vries <tom@codesourcery.com>
PR tree-optimization/67476
* doc/invoke.texi (@item parloops-schedule): New item.
* params.def (PARAM_PARLOOPS_SCHEDULE): New DEFPARAMENUM5.
* tree-parloops.c: Include params-enum.h.
(create_parallel_loop): Handle PARAM_PARLOOPS_SCHEDULE.
* testsuite/libgomp.c/autopar-3.c: New test.
* testsuite/libgomp.c/autopar-4.c: New test.
* testsuite/libgomp.c/autopar-5.c: New test.
* testsuite/libgomp.c/autopar-6.c: New test.
* testsuite/libgomp.c/autopar-7.c: New test.
* testsuite/libgomp.c/autopar-8.c: New test.
Added:
trunk/libgomp/testsuite/libgomp.c/autopar-3.c
trunk/libgomp/testsuite/libgomp.c/autopar-4.c
trunk/libgomp/testsuite/libgomp.c/autopar-5.c
trunk/libgomp/testsuite/libgomp.c/autopar-6.c
trunk/libgomp/testsuite/libgomp.c/autopar-7.c
trunk/libgomp/testsuite/libgomp.c/autopar-8.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/doc/invoke.texi
trunk/gcc/params.def
trunk/gcc/tree-parloops.c
trunk/libgomp/ChangeLog
next prev parent reply other threads:[~2015-10-13 10:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 9:12 [Bug tree-optimization/67476] New: " vries at gcc dot gnu.org
2015-09-07 9:13 ` [Bug tree-optimization/67476] " vries at gcc dot gnu.org
2015-09-07 9:25 ` vries at gcc dot gnu.org
2015-09-10 9:30 ` vries at gcc dot gnu.org
2015-09-11 10:56 ` vries at gcc dot gnu.org
2015-09-14 15:32 ` vries at gcc dot gnu.org
2015-09-15 13:09 ` vries at gcc dot gnu.org
2015-09-22 7:20 ` vries at gcc dot gnu.org
2015-10-12 14:14 ` vries at gcc dot gnu.org
2015-10-12 14:14 ` vries at gcc dot gnu.org
2015-10-13 10:09 ` vries at gcc dot gnu.org [this message]
2015-10-14 7:08 ` vries at gcc dot gnu.org
2015-10-14 14:30 ` vries at gcc dot gnu.org
2015-10-14 14:30 ` vries at gcc dot gnu.org
2015-10-14 14:30 ` vries at gcc dot gnu.org
2015-10-14 14:31 ` 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-67476-4-FgXCJRMiUF@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: link
Be 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).