public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "razya at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/38168]  New: failure in gamess benchmark when -ftree-parallelize-loops=4 is enabled
Date: Mon, 17 Nov 2008 12:25:00 -0000	[thread overview]
Message-ID: <bug-38168-11721@http.gcc.gnu.org/bugzilla/> (raw)

specperl /Develop/SPEC2006/bin/specpp  -DSPEC_CPU_NO_HOLLERITH -DSPEC_CPU
-DNDEBUG   chgpen.F -o chgpen.fppized.f

/Develop/Bins/bin//gfortran  -c -o chgpen.fppized.o   -O3 -mcpu=power6
-mtune=power6 -ftree-parallelize-loops=4                 chgpen.fppized.f
chgpen.fppized.f: In function 'stepit':
chgpen.fppized.f:1726: error: basic block 425 should be marked irreducible
chgpen.fppized.f:1726: error: edge from 425 to 418 should be marked irreducible
chgpen.fppized.f:1726: error: basic block 418 should be marked irreducible
chgpen.fppized.f:1726: error: edge from 418 to 68 should be marked irreducible
chgpen.fppized.f:1726: confused by earlier errors, bailing out


-- 
           Summary: failure in gamess benchmark when -ftree-parallelize-
                    loops=4 is enabled
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: razya at il dot ibm dot com
 GCC build triplet: powerpc64-suse-linux
  GCC host triplet: powerpc64-suse-linux
GCC target triplet: powerpc64-suse-linux


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


                 reply	other threads:[~2008-11-17 12:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-38168-11721@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).