public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/44959] [4.5 Regression] bootstrap failed at Comparing stages 2 and 3 Date: Mon, 07 May 2012 12:42:00 -0000 [thread overview] Message-ID: <bug-44959-4-qWPNclDFGt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-44959-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44959 --- Comment #17 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2012-05-07 12:37:37 UTC --- While the checksum files are expected to differ (thus there are only warnings about them), the size increase looks really strange: in my current 4.6.4 build on alpha-dec-osf5.1b I have -rw-r--r-- 1 ro gcc 22944 May 6 05:01 gcc/cc1-checksum.o -rw-r--r-- 1 ro gcc 22944 May 6 03:38 prev-gcc/cc1-checksum.o -rw-r--r-- 1 ro gcc 28504 May 5 23:58 stage1-gcc/cc1-checksum.o Could you please attach the one smallest of the non *-checksum.o differing files from all 3 stages for investigation? Thanks. Rainer
next prev parent reply other threads:[~2012-05-07 12:41 UTC|newest] Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-44959-4@http.gcc.gnu.org/bugzilla/> 2010-11-14 12:01 ` rguenth at gcc dot gnu.org 2010-12-15 1:53 ` htl10 at users dot sourceforge.net 2010-12-16 13:28 ` rguenth at gcc dot gnu.org 2010-12-17 12:22 ` htl10 at users dot sourceforge.net 2011-04-28 15:40 ` rguenth at gcc dot gnu.org 2011-04-30 7:17 ` htl10 at users dot sourceforge.net 2011-04-30 11:00 ` htl10 at users dot sourceforge.net 2011-07-19 12:27 ` ro at gcc dot gnu.org 2011-08-02 11:08 ` htl10 at users dot sourceforge.net 2011-08-02 11:11 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-08-03 15:30 ` htl10 at users dot sourceforge.net 2011-08-03 15:33 ` htl10 at users dot sourceforge.net 2011-08-05 5:39 ` htl10 at users dot sourceforge.net 2012-05-07 7:09 ` htl10 at users dot sourceforge.net 2012-05-07 10:28 ` htl10 at users dot sourceforge.net 2012-05-07 12:42 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message] 2012-05-08 14:08 ` htl10 at users dot sourceforge.net 2012-05-08 14:09 ` htl10 at users dot sourceforge.net 2012-05-08 14:16 ` htl10 at users dot sourceforge.net 2012-05-08 14:28 ` htl10 at users dot sourceforge.net 2012-05-08 15:37 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-05-08 20:50 ` htl10 at users dot sourceforge.net 2012-07-02 9:44 ` [Bug bootstrap/44959] [4.6 " rguenth at gcc dot gnu.org 2012-08-30 14:05 ` htl10 at users dot sourceforge.net 2012-08-30 14:19 ` htl10 at users dot sourceforge.net 2012-08-30 14:57 ` htl10 at users dot sourceforge.net 2012-08-30 17:32 ` htl10 at users dot sourceforge.net 2012-09-01 2:53 ` htl10 at users dot sourceforge.net 2012-09-01 8:18 ` htl10 at users dot sourceforge.net 2012-09-01 8:26 ` pinskia at gcc dot gnu.org 2012-09-01 11:23 ` htl10 at users dot sourceforge.net 2012-09-14 13:43 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-14 13:44 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-14 13:49 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-14 13:52 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-14 13:54 ` ro at CeBiTec dot Uni-Bielefeld.DE 2012-09-14 14:43 ` htl10 at users dot sourceforge.net 2013-04-12 16:13 ` jakub at gcc dot gnu.org 2013-04-15 12:51 ` ro at CeBiTec dot Uni-Bielefeld.DE 2013-11-10 8:11 ` pinskia at gcc dot gnu.org 2013-12-30 4:26 ` htl10 at users dot sourceforge.net 2013-12-30 4:58 ` htl10 at users dot sourceforge.net 2014-01-03 11:10 ` ro at CeBiTec dot Uni-Bielefeld.DE 2010-07-15 21:49 [Bug bootstrap/44959] New: [4.5 " htl10 at users dot sourceforge dot net 2010-07-16 8:30 ` [Bug bootstrap/44959] " rguenth at gcc dot gnu dot org 2010-07-22 8:55 ` rguenth at gcc dot gnu dot org 2010-07-31 9:35 ` rguenth at gcc dot gnu dot 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-44959-4-qWPNclDFGt@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).