public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/55051] New: [4.8 Regression] profiledbootstrap failed Date: Wed, 24 Oct 2012 10:22:00 -0000 [thread overview] Message-ID: <bug-55051-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55051 Bug #: 55051 Summary: [4.8 Regression] profiledbootstrap failed Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned@gcc.gnu.org ReportedBy: hjl.tools@gmail.com On Linux/x86-64, revision 192538 gave # make profiledbootstrap -j8 ... In file included from /export/gnu/import/git/gcc/gcc/gcov-dump.c:30:0: /export/gnu/import/git/gcc/gcc/gcov-io.c:554:54: error: array subscript is above array bounds [-Werror=array-bounds] cur_bitvector = histo_bitvector[bv_ix++]; ^ cc1plus: all warnings being treated as errors make[4]: *** [gcov-dump.o] Error 1 make[4]: *** Waiting for unfinished jobs.... In file included from /export/gnu/import/git/gcc/gcc/gcov.c:47:0: /export/gnu/import/git/gcc/gcc/gcov-io.c: In function ‘int read_count_file(function_t*)’: /export/gnu/import/git/gcc/gcc/gcov-io.c:554:54: error: array subscript is above array bounds [-Werror=array-bounds] cur_bitvector = histo_bitvector[bv_ix++]; ^ cc1plus: all warnings being treated as errors make[4]: *** [gcov.o] Error 1 Revision 192529 is OK.
next reply other threads:[~2012-10-24 10:22 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-24 10:22 hjl.tools at gmail dot com [this message] 2012-10-24 10:22 ` [Bug bootstrap/55051] " hjl.tools at gmail dot com 2012-10-24 23:50 ` hjl.tools at gmail dot com 2012-10-25 0:49 ` hjl.tools at gmail dot com 2012-10-25 6:52 ` ubizjak at gmail dot com 2012-11-14 15:07 ` hjl.tools at gmail dot com 2012-11-14 15:09 ` hjl.tools at gmail dot com 2012-11-14 15:13 ` markus at trippelsdorf dot de 2012-11-14 15:35 ` hubicka at ucw dot cz 2012-11-14 20:48 ` markus at trippelsdorf dot de 2012-11-14 23:03 ` hubicka at gcc dot gnu.org 2012-11-15 0:07 ` hubicka at gcc dot gnu.org 2012-11-15 0:22 ` tejohnson at google dot com 2012-11-15 0:31 ` hjl.tools at gmail dot com 2012-11-15 1:03 ` hubicka at gcc dot gnu.org 2012-11-15 1:07 ` hubicka at gcc dot gnu.org 2012-11-15 1:10 ` hubicka at gcc dot gnu.org 2012-11-15 1:18 ` hubicka at gcc dot gnu.org 2012-11-15 1:29 ` tejohnson at google dot com 2012-11-15 1:34 ` tejohnson at google dot com 2012-11-15 1:42 ` Jan Hubicka 2012-11-15 1:43 ` hubicka at ucw dot cz 2012-11-15 1:53 ` tejohnson at google dot com 2012-11-15 2:02 ` hubicka at ucw dot cz 2012-11-15 2:46 ` tejohnson at google dot com 2012-11-15 6:44 ` tejohnson at google dot com 2012-11-15 10:56 ` Jan Hubicka 2012-11-15 10:57 ` hubicka at ucw dot cz 2012-11-15 14:34 ` tejohnson at google dot com 2012-11-15 22:42 ` tejohnson at google dot com 2012-11-16 17:42 ` hubicka at gcc dot gnu.org 2012-11-16 18:03 ` tejohnson at google dot com 2012-11-16 18:57 ` hubicka at ucw dot cz 2012-11-19 5:21 ` tejohnson at gcc dot gnu.org 2012-12-07 12:04 ` 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-55051-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: 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).