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 debug/34249] [4.3 Regression] FAIL: gcc.dg/tree-prof/bb-reorg.c compilation, -fprofile-use -D_PROFILE_USE
Date: Wed, 16 Jan 2008 17:52:00 -0000 [thread overview]
Message-ID: <20080116172547.22442.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34249-682@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from ubizjak at gmail dot com 2008-01-16 17:25 -------
(In reply to comment #8)
> It isn't fixed. The error went from as to ld:
Here is my log:
Executing on host: /home/uros/gcc-build-all/gcc/xgcc
-B/home/uros/gcc-build-all/gcc/ /home/uros/gcc-svn/trunk/gcc/
testsuite/gcc.dg/tree-prof/bb-reorg.c -O2 -freorder-blocks-and-partition
-fprofile-use -D_PROFILE_USE -fno-show-
column -lm -o /home/uros/gcc-build-all/gcc/testsuite/gcc/bb-reorg.x02
(timeout = 300)
PASS: gcc.dg/tree-prof/bb-reorg.c compilation, -fprofile-use -D_PROFILE_USE
Setting LD_LIBRARY_PATH to
:/home/uros/gcc-build-all/gcc:/home/uros/gcc-build-all/gcc/32::/home/uros/gcc-build-all
/gcc:/home/uros/gcc-build-all/gcc/32:/usr/local/lib64:/usr/lib/xorg:/usr/lib64/xorg
PASS: gcc.dg/tree-prof/bb-reorg.c execution, -fprofile-use -D_PROFILE_USE
testcase /home/uros/gcc-svn/trunk/gcc/testsuite/gcc.dg/tree-prof/tree-prof.exp
completed in 2 seconds
GNU ld version 2.17.50.0.3-6 20060715
The difference between non-working (.s_) and working (.s) asm dump is:
--- bb-reorg.s_ 2008-01-16 18:22:01.000000000 +0100
+++ bb-reorg.s 2008-01-16 18:22:40.000000000 +0100
@@ -147,9 +147,12 @@
.LASFDE3:
.long .LASFDE3-.Lframe1
.long .LFB15
- .long .LFE15-.LFB15
+ .long .LHOTB1
+ .long .LHOTE1-.LHOTB1
+ .long .LCOLDB1
+ .long .LCOLDE1-.LCOLDB1
.uleb128 0x0
.align 8
.LEFDE3:
- .ident "GCC: (GNU) 4.3.0 20080107 (experimental) [trunk revision
131375]"
+ .ident "GCC: (GNU) 4.3.0 20080114 (experimental) [trunk revision
131520]"
.section .note.GNU-stack,"",@progbits
Is the problem with binutils here?
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |WAITING
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34249
next prev parent reply other threads:[~2008-01-16 17:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 12:36 [Bug rtl-optimization/34249] New: " hjl at lucon dot org
2007-11-27 12:50 ` [Bug rtl-optimization/34249] " hjl at lucon dot org
2007-11-27 14:06 ` rguenth at gcc dot gnu dot org
2007-12-02 23:52 ` pinskia at gcc dot gnu dot org
2008-01-14 14:21 ` [Bug rtl-optimization/34249] [4.3 Regression] " ubizjak at gmail dot com
2008-01-14 15:32 ` [Bug debug/34249] " ubizjak at gmail dot com
2008-01-14 19:20 ` ubizjak at gmail dot com
2008-01-16 9:02 ` ubizjak at gmail dot com
2008-01-16 11:47 ` uros at gcc dot gnu dot org
2008-01-16 11:50 ` ubizjak at gmail dot com
2008-01-16 16:47 ` hjl at lucon dot org
2008-01-16 17:52 ` ubizjak at gmail dot com [this message]
2008-01-16 18:38 ` ubizjak at gmail dot com
2008-01-16 18:47 ` hjl at lucon dot org
2008-01-16 18:59 ` ubizjak at gmail dot com
2008-01-16 20:43 ` hjl at lucon dot org
2008-01-16 21:36 ` uros at gcc dot gnu dot org
2008-01-16 21:47 ` ubizjak at gmail 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=20080116172547.22442.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).