public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/60082] New: Certain Cilk keywords executable Hanging for -O1
@ 2014-02-05 17:06 bviyer at gmail dot com
  2014-02-05 17:06 ` [Bug c++/60082] " bviyer at gmail dot com
                   ` (6 more replies)
  0 siblings, 7 replies; 8+ messages in thread
From: bviyer at gmail dot com @ 2014-02-05 17:06 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60082

            Bug ID: 60082
           Summary: Certain Cilk keywords executable Hanging for -O1
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bviyer at gmail dot com

The following two Cilk Plus tests is timing out at -O1 in my x86_64 box (-O2,
-O3  and -O0 works fine). These tests were working fine till revision r207047.
Some check-in between r207047 and r207437 seem to have caused it. Can someone
please look at this? It looks like a middle-end/back-end issue.

WARNING: program timed out.
FAIL: g++.dg/cilk-plus/CK/catch_exc.cc  -O1 -fcilkplus execution test
WARNING: program timed out.
FAIL: c-c++-common/cilk-plus/CK/spawner_inline.c  -O1 execution test

Thanks,

Balaji V. Iyer.


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2015-02-24 19:43 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-02-05 17:06 [Bug c++/60082] New: Certain Cilk keywords executable Hanging for -O1 bviyer at gmail dot com
2014-02-05 17:06 ` [Bug c++/60082] " bviyer at gmail dot com
2014-02-05 18:17 ` dominiq at lps dot ens.fr
2014-02-05 18:18 ` dominiq at lps dot ens.fr
2014-02-05 18:33 ` dominiq at lps dot ens.fr
2014-02-07 10:49 ` jakub at gcc dot gnu.org
2014-02-07 13:01 ` jakub at gcc dot gnu.org
2015-02-24 20:54 ` law at redhat dot com

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).