public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gcc at breakpoint dot cc" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/36047] -pg does not work on large binaries and m68k
Date: Wed, 22 Apr 2009 18:42:00 -0000	[thread overview]
Message-ID: <20090422184153.28216.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36047-14399@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from gcc at breakpoint dot cc  2009-04-22 18:41 -------
Wasn't 

# echo 'int main(void) { return 0; }' > file.c

not enough or did you overlook that part? 

The -E output is pretty much the same, it is:

$ cat test.i 
# 1 "test.c"
# 1 "<built-in>"
# 1 "<command-line>"
# 1 "test.c"
int main(void)
{
 return 0;
}


---
The -S output (I guess you meant that) would be:

$ m68k-linux-gnu-gcc -o test.S test.c -static -pg -S && cat test.S 
#NO_APP
        .file   "test.c"
        .text
        .align  2
        .globl  main
        .type   main, @function
main:
        link.w %fp,#0
        .data
        .align  2
.LP2:
        .long   0
        .text
        lea (.LP2,%pc),%a1
        jbsr _mcount
        clr.l %d0
        unlk %fp
        rts
        .size   main, .-main
        .ident  "GCC: (Sourcery G++ Lite 4.3-43) 4.3.2"
        .section        .note.GNU-stack,"",@progbits
---- 

And my rec for the fix was to get rid of the lea before the branch to the
_mcount call. However someone might need it, I'm not sure.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36047


  parent reply	other threads:[~2009-04-22 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-25 15:05 [Bug c/36047] New: " gcc at breakpoint dot cc
2008-07-24 19:49 ` [Bug target/36047] " gcc at breakpoint dot cc
2009-03-16 11:36 ` mkuvyrkov at gcc dot gnu dot org
2009-04-22 18:42 ` gcc at breakpoint dot cc [this message]
2009-11-04 16:58 ` mkuvyrkov at gcc dot gnu dot org
2009-11-19 10:10 ` mkuvyrkov at gcc dot gnu dot org
2009-12-11 15:32 ` mkuvyrkov at gcc dot gnu dot org
2009-12-11 15:36 ` mkuvyrkov 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=20090422184153.28216.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).