public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/32468] number of threads in a parallel region depends on number of SECTIONs and MAX_THREADS Date: Mon, 02 Jul 2007 19:23:00 -0000 [thread overview] Message-ID: <20070702192258.20951.qmail@sourceware.org> (raw) In-Reply-To: <bug-32468-14710@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from jakub at gcc dot gnu dot org 2007-07-02 19:22 ------- Subject: Bug 32468 Author: jakub Date: Mon Jul 2 19:22:47 2007 New Revision: 126226 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=126226 Log: PR libgomp/32468 * omp-low.c (check_combined_parallel): New function. (lower_omp_parallel): Call it via walk_stmts, set OMP_PARALLEL_COMBINED if appropriate. (determine_parallel_type): If OMP_FOR resp. OMP_SECTIONS isn't the only statement in WS_ENTRY_BB or OMP_RETURN the only one in PAR_EXIT_BB and not OMP_PARALLEL_COMBINED, don't consider it as combined parallel. * gcc.dg/gomp/pr32468-1.c: New test. Added: trunk/gcc/testsuite/gcc.dg/gomp/pr32468-1.c Modified: trunk/gcc/ChangeLog trunk/gcc/omp-low.c trunk/gcc/testsuite/ChangeLog -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32468
next prev parent reply other threads:[~2007-07-02 19:23 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-22 19:56 [Bug fortran/32468] New: PRESENCE OF SECTIONS W/ 1 SECTION CAUSES PARALLEL REGION TO HAVE 1 THREAD, NOT 4 longb at cray dot com 2007-06-22 21:37 ` [Bug fortran/32468] number of threads in a parallel region depends on number of SECTIONs and MAX_THREADS dfranke at gcc dot gnu dot org 2007-06-22 21:54 ` jakub at gcc dot gnu dot org 2007-07-02 12:20 ` [Bug libgomp/32468] " jakub at gcc dot gnu dot org 2007-07-02 19:19 ` jakub at gcc dot gnu dot org 2007-07-02 19:23 ` jakub at gcc dot gnu dot org [this message] 2007-07-02 19:26 ` jakub at gcc dot gnu dot org 2007-07-02 19:27 ` jakub at gcc dot gnu dot org 2007-07-02 19:28 ` jakub at gcc dot gnu dot 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=20070702192258.20951.qmail@sourceware.org \ --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).