public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/60013] New: Build of 176.gcc from CPU2000 loops in cc1 starting with revision 207231
Date: Fri, 31 Jan 2014 20:05:00 -0000	[thread overview]
Message-ID: <bug-60013-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 60013
           Summary: Build of 176.gcc from CPU2000 loops in cc1 starting
                    with revision 207231
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pthaugen at gcc dot gnu.org
                CC: bergner at gcc dot gnu.org, dje at gcc dot gnu.org,
                    jakub at gcc dot gnu.org
              Host: powerpc64-linux
            Target: powerpc64-linux
             Build: powerpc64-linux

Created attachment 32006
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32006&action=edit
preprocessed source

Compile of file fold-const.c from 176.gcc in cpu2000 loops starting with
r207231. Compile command 'gcc -c -m64 -O2 fold-const.i'. Stopping in debugger
(a few different times) gives backtrace like the following.

(gdb) bt
#0  add_clause (conditions=0xfffade90400, p=0xfffffffdec0, clause=<optimized
out>)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:360
#1  0x000000001047dc6c in or_predicates (conditions=0xfffade90400, p=<optimized
out>, 
    p2=<optimized out>) at
/home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:461
#2  0x0000000010485e94 in compute_bb_predicates (node=<optimized out>, 
    parms_info=<optimized out>, summary=0xfffb027ccc8)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:1873
#3  0x0000000010487cdc in estimate_function_body_sizes (node=0xfffafec30b0, 
    early=<optimized out>)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:2405
#4  0x000000001048a08c in compute_inline_parameters (node=0xfffafec30b0, 
    early=<optimized out>)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:2797
#5  0x000000001048a554 in inline_analyze_function (node=0xfffafec30b0)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:3790
#6  0x000000001048a7f8 in inline_generate_summary ()
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/ipa-inline-analysis.c:3841
#7  0x0000000010590920 in execute_ipa_summary_passes (ipa_pass=0x112f66d0)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/passes.c:2027
#8  0x0000000010272494 in ipa_passes ()
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/cgraphunit.c:2060
#9  compile () at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/cgraphunit.c:2164
#10 0x0000000010273ae8 in finalize_compilation_unit ()
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/cgraphunit.c:2319
#11 0x00000000100df164 in c_write_global_declarations ()
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/c/c-decl.c:10401
#12 0x00000000106687c4 in compile_file ()
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/toplev.c:562
#13 0x0000000010669d0c in do_compile ()
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/toplev.c:1914
#14 toplev_main (argc=12, argv=0xffffffff038)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/toplev.c:1990
#15 0x0000000010c92e40 in main (argc=<optimized out>, argv=<optimized out>)
    at /home/pthaugen/src/gcc/gcc_hunt/gcc/gcc/main.c:36


             reply	other threads:[~2014-01-31 20:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31 20:05 pthaugen at gcc dot gnu.org [this message]
2014-01-31 20:11 ` [Bug middle-end/60013] " hjl.tools at gmail dot com
2014-02-01 16:06 ` [Bug middle-end/60013] [4.9 Regression] Build of 176.gcc from CPU2000 loops in cc1 starting with r207231 hjl.tools at gmail dot com
2014-02-01 16:42 ` hjl.tools at gmail dot com
2014-02-01 17:37 ` jakub at gcc dot gnu.org
2014-02-01 17:40 ` hjl.tools at gmail dot com
2014-02-01 17:43 ` hjl.tools at gmail dot com
2014-02-01 18:04 ` hjl.tools at gmail dot com
2014-02-01 19:08 ` jakub at gcc dot gnu.org
2014-02-02 16:39 ` hjl.tools at gmail dot com
2014-02-02 18:28 ` hjl.tools at gmail dot com
2014-02-03  9:46 ` rguenth at gcc dot gnu.org
2014-02-04 17:30 ` jakub at gcc dot gnu.org
2014-02-04 21:32 ` jakub at gcc dot gnu.org
2014-02-05  7:09 ` jakub at gcc dot gnu.org
2014-02-05 23:22 ` pthaugen at gcc dot gnu.org
2014-02-06  7:40 ` hubicka at gcc dot gnu.org
2014-02-06  8:54 ` 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-60013-4@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).