public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/52444] gcc.dg/tree-prof/pr44777.c execution, -fprofile-generate -D_PROFILE_GENERATE fails at -m32
Date: Sat, 15 Dec 2012 14:17:00 -0000 [thread overview]
Message-ID: <bug-52444-4-nDfjSAMHl4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52444-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52444
--- Comment #3 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-12-15 14:17:18 UTC ---
One interesting thing is that slightly different assembly is generated each
time you recompile this test case...
# diff -u pr44777.s pr44777.s.PROFILE_GENERATE
--- pr44777.s 2012-12-15 09:10:30.000000000 -0500
+++ pr44777.s.PROFILE_GENERATE 2012-12-15 09:08:44.000000000 -0500
@@ -262,7 +262,7 @@
LPBX0:
.long 875575397
.long 0
- .long -1629035081
+ .long -1629140997
.long LC0
.long ___gcov_merge_add
.long 0
--- pr44777.s 2012-12-15 09:11:23.000000000 -0500+++
pr44777.s.PROFILE_GENERATE 2012-12-15 09:08:44.000000000 -0500
@@ -262,7 +262,7 @@
LPBX0:
.long 875575397
.long 0
- .long -1628981943
+ .long -1629140997
.long LC0
.long ___gcov_merge_add
.long 0
next prev parent reply other threads:[~2012-12-15 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 2:51 [Bug c/52444] New: " howarth at nitro dot med.uc.edu
2012-12-15 14:02 ` [Bug c/52444] " howarth at nitro dot med.uc.edu
2012-12-15 14:15 ` howarth at nitro dot med.uc.edu
2012-12-15 14:17 ` howarth at nitro dot med.uc.edu [this message]
2012-12-15 14:23 ` howarth at nitro dot med.uc.edu
2012-12-15 18:15 ` [Bug target/52444] non-local gotos are broken on x86 darwin pinskia 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-52444-4-nDfjSAMHl4@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: 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).