public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "izamyatin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53161] [4.8 Regression] ICE with weakref function and a function which takes vector types
Date: Fri, 11 May 2012 10:08:00 -0000	[thread overview]
Message-ID: <bug-53161-4-2bgLijOqVn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53161-4@http.gcc.gnu.org/bugzilla/>

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

Igor Zamyatin <izamyatin at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |izamyatin at gmail dot com

--- Comment #6 from Igor Zamyatin <izamyatin at gmail dot com> 2012-05-11 10:00:51 UTC ---
I also see that LTO bootstrap fails with following message

../../src-trunk/gcc/gcov.c:2348:1: internal compiler error: vector
VEC(inline_edge_summary_t,base) index domain error, in inline_edge_summary at
ipa-inline.h:200
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
make[6]: *** [gcov.o] Error 1
make[6]: *** Waiting for unfinished jobs....
rm gcj-dbtool.pod jcf-dump.pod jv-convert.pod grmic.pod gcj.pod gc-analyze.pod
gcov.pod gfdl.pod cpp.pod gij.pod gfortran.pod gcc.pod fsf-funding.pod
make[6]: Leaving directory `/export/gnu/import/git/gcc-test-profile/bld/gcc'
make[5]: *** [all-stageprofile-gcc] Error 2
make[5]: Leaving directory `/export/gnu/import/git/gcc-test-profile/bld'
make[4]: *** [stageprofile-bubble] Error 2
make[4]: Leaving directory `/export/gnu/import/git/gcc-test-profile/bld'
make[3]: *** [profiledbootstrap] Error 2
make[3]: Leaving directory `/export/gnu/import/git/gcc-test-profile/bld'
6968.90user 244.95system 24:30.58elapsed 490%CPU (0avgtext+0avgdata
567304maxresident)k
16256inputs+8351248outputs (112major+65804975minor)pagefaults 0swaps
make[2]: *** [profiledbootstrap] Error 2
make[2]: Leaving directory `/export/gnu/import/git/gcc-test-profile'


  parent reply	other threads:[~2012-05-11 10:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-29 20:15 [Bug c++/53161] New: index domain error, in ipa_remove_reference at ipa-ref.c:84 dcb314 at hotmail dot com
2012-04-29 20:16 ` [Bug c++/53161] " dcb314 at hotmail dot com
2012-04-29 20:24 ` [Bug middle-end/53161] " pinskia at gcc dot gnu.org
2012-04-30  4:15 ` [Bug middle-end/53161] [4.8 Regression] ICE with weakref function and a function which takes vector types pinskia at gcc dot gnu.org
2012-04-30 14:04 ` hjl.tools at gmail dot com
2012-04-30 15:17 ` hubicka at gcc dot gnu.org
2012-05-11 10:08 ` izamyatin at gmail dot com
2012-05-11 10:08 ` izamyatin at gmail dot com [this message]
2012-05-21 21:05 ` roman at binarylife dot net
2012-05-22 13:25 ` hubicka at gcc dot gnu.org
2012-05-23  9:28 ` hubicka at gcc dot gnu.org
2012-09-07 11:43 ` rguenth 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-53161-4-2bgLijOqVn@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).