public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/38977] [4.4 Regression] bash no longer builds with profile-feedback Date: Tue, 27 Jan 2009 17:02:00 -0000 [thread overview] Message-ID: <20090127170142.32343.qmail@sourceware.org> (raw) In-Reply-To: <bug-38977-10053@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from rguenth at gcc dot gnu dot org 2009-01-27 17:01 ------- Hm, unfortunately simply disabling that error doesn't fix my bash build. Instead we now error on jobs.c:4121: error: corrupted profile info: number of executions for edge 10-11 thought to be -1726 jobs.c:4121: error: corrupted profile info: number of executions for edge 10-12 thought to be 1745 jobs.c:4121: error: corrupted profile info: number of iterations for basic block 11 thought to be -120 which is an error that is present also in 4.3. So I guess there is some real bug wrt profiling in gcc 4.4. -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|rguenth at gcc dot gnu dot |unassigned at gcc dot gnu |org |dot org Status|ASSIGNED |NEW http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38977
next prev parent reply other threads:[~2009-01-27 17:02 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-26 12:47 [Bug tree-optimization/38977] New: " rguenth at gcc dot gnu dot org 2009-01-26 14:04 ` [Bug tree-optimization/38977] " rguenth at gcc dot gnu dot org 2009-01-27 7:02 ` jakub at gcc dot gnu dot org 2009-01-27 16:25 ` rguenth at gcc dot gnu dot org 2009-01-27 17:02 ` rguenth at gcc dot gnu dot org [this message] 2009-01-28 12:48 ` rguenth at gcc dot gnu dot org 2009-01-28 17:08 ` doko at ubuntu dot com 2009-01-28 21:38 ` rguenth at gcc dot gnu dot org 2009-01-30 16:35 ` rguenth at gcc dot gnu dot org 2009-01-30 16:54 ` jakub at gcc dot gnu dot org 2009-01-30 17:13 ` matz at gcc dot gnu dot org 2009-01-30 17:23 ` jakub at gcc dot gnu dot org 2009-01-31 14:38 ` bonzini at gnu dot org 2009-02-02 16:27 ` sje at cup dot hp dot com 2009-02-02 16:46 ` rguenth at gcc dot gnu dot org 2009-02-04 8:19 ` jakub at gcc dot gnu dot org 2009-02-04 19:51 ` jakub at gcc dot gnu dot org 2009-02-04 22:51 ` rguenth at gcc dot gnu dot org 2009-02-04 23:16 ` rguenth at gcc dot gnu dot org 2009-02-05 13:37 ` rguenth at gcc dot gnu dot org 2009-02-05 15:31 ` rguenth at gcc dot gnu dot org 2009-02-05 15:37 ` rguenth at gcc dot gnu dot org 2009-02-05 22:14 ` rguenth at gcc dot gnu dot org 2009-02-06 9:07 ` rguenth at gcc dot gnu dot org 2009-02-06 9:08 ` rguenth at gcc dot gnu dot org 2009-02-12 13:40 ` doko at ubuntu dot com
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=20090127170142.32343.qmail@sourceware.org \ --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).