public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/34999] Fallthru crossing edges in partition_hot_cold_basic_blocks are not been fixed when the section ends with call insn
Date: Thu, 28 Feb 2008 18:35:00 -0000 [thread overview]
Message-ID: <20080228183422.20377.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34999-13229@http.gcc.gnu.org/bugzilla/>
------- Comment #8 from ubizjak at gmail dot com 2008-02-28 18:34 -------
(In reply to comment #7)
> Thanks, unfortunately I still can not reproduce the fail.
Probably you need newer binutils:
GNU ld (GNU Binutils) 2.18
Executing on host: /home/uros/gcc-build/gcc/xgcc -B/home/uros/gcc-build/gcc/
/home/uros/gcc-svn/trunk/gcc/testsuite/gcc.dg/tree-prof/pr34999.c -O2
-freorder-blocks-and-partition -fprofile-use -D_PROFILE_USE -fno-show-column
-lm -o /home/uros/gcc-build/gcc/testsuite/gcc/pr34999.x02 (timeout = 300)
/usr/local/x86_64-unknown-linux-gnu/bin/ld: error in
/tmp/cceUz9XT.o(.eh_frame); no .eh_frame_hdr table will be created.^M
output is:
/usr/local/x86_64-unknown-linux-gnu/bin/ld: error in
/tmp/cceUz9XT.o(.eh_frame); no .eh_frame_hdr table will be created.^M
FAIL: gcc.dg/tree-prof/pr34999.c compilation, -fprofile-use -D_PROFILE_USE
UNRESOLVED: gcc.dg/tree-prof/pr34999.c execution, -fprofile-use
-D_PROFILE_USE
HJ, is this a binutils bug or gcc bug?
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl dot tools at gmail dot
| |com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34999
next prev parent reply other threads:[~2008-02-28 18:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 16:20 [Bug rtl-optimization/34999] New: " eres at il dot ibm dot com
2008-01-28 16:28 ` [Bug rtl-optimization/34999] " eres at il dot ibm dot com
2008-01-29 17:12 ` eres at il dot ibm dot com
2008-02-27 13:29 ` revitale at gcc dot gnu dot org
2008-02-28 9:48 ` ubizjak at gmail dot com
2008-02-28 13:01 ` eres at il dot ibm dot com
2008-02-28 13:27 ` ubizjak at gmail dot com
2008-02-28 13:50 ` eres at il dot ibm dot com
2008-02-28 18:35 ` ubizjak at gmail dot com [this message]
2008-02-28 19:13 ` ubizjak at gmail dot com
2008-02-29 5:23 ` eres at il dot ibm dot com
2008-02-29 5:54 ` hjl dot tools at gmail dot com
2008-02-29 6:08 ` ubizjak at gmail dot com
2008-02-29 6:33 ` ubizjak at gmail dot com
2008-02-29 6:48 ` ubizjak at gmail dot com
2008-02-29 8:57 ` jakub at gcc dot gnu dot org
2008-03-04 14:51 ` uweigand at gcc dot gnu dot org
2008-03-04 15:10 ` jakub at gcc dot gnu dot org
2008-03-16 16:28 ` danglin at gcc dot gnu dot org
2008-04-08 11:07 ` eres at il dot ibm dot com
2008-04-08 11:14 ` jakub at gcc dot gnu dot org
2008-12-29 2:41 ` pinskia at gcc dot gnu dot org
2009-03-27 16:37 ` ghazi at gcc dot gnu dot org
2009-03-27 17:27 ` steven at gcc dot gnu dot org
2009-07-24 15:37 ` [Bug rtl-optimization/34999] Incorrect FDE entries with hot/cold code section splitting (partition_hot_cold_basic_blocks) jakub at gcc dot gnu dot org
2009-07-24 23:31 ` jakub at gcc dot gnu dot org
2009-08-06 19:54 ` ghazi at gcc dot gnu dot org
2009-09-07 1:04 ` ghazi at gcc dot gnu dot org
2009-12-01 15:14 ` ghazi at gcc dot gnu dot org
2009-12-01 15:16 ` 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=20080228183422.20377.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: 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).