public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/59779] [4.9 Regression] FAIL: gcc.dg/autopar/outer-1.c scan-tree-dump-times parloops "parallelizing outer loop" Date: Wed, 12 Mar 2014 13:55:00 -0000 [thread overview] Message-ID: <bug-59779-4-Lb71wM6xWP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59779-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59779 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Can't reproduce this with a cross-compiler to hppa-unknown-linux on current trunk: ./cc1 -O2 -quiet -ftree-parallelize-loops=4 -fdump-tree-parloops-details -fdump-tree-optimized outer-1.c -nostdinc; grep 'parallelizing outer loop' outer-1.c.112t.parloops; grep loopfn outer-1.c.169t.optimized parallelizing outer loop 9 __builtin_GOMP_parallel (parloop._loopfn.0, &.paral_data_store.8, 4, 0); ;; Function parloop._loopfn.0 (parloop._loopfn.0, funcdef_no=2, decl_uid=1447, symbol_order=3) parloop._loopfn.0 (void * .paral_data_param)
next prev parent reply other threads:[~2014-03-12 13:55 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-12 19:50 [Bug tree-optimization/59779] New: " danglin at gcc dot gnu.org 2014-01-12 19:50 ` [Bug tree-optimization/59779] " danglin at gcc dot gnu.org 2014-01-13 9:55 ` rguenth at gcc dot gnu.org 2014-03-12 13:55 ` jakub at gcc dot gnu.org [this message] 2014-03-13 1:39 ` dave.anglin at bell dot net 2014-03-13 8:44 ` jakub at gcc dot gnu.org 2014-03-13 10:31 ` jakub at gcc dot gnu.org 2014-03-13 11:33 ` jakub at gcc dot gnu.org 2014-03-13 19:10 ` jakub 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-59779-4-Lb71wM6xWP@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).