public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/47071] Using -ffunction-sections produces bad assembler on my testcase
Date: Mon, 27 Dec 2010 20:19:00 -0000	[thread overview]
Message-ID: <bug-47071-4-YA3yL2WFQm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47071-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|assemble-failure            |
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2010-12-27 20:19:34 UTC ---
Your testcase is invalid as you don't change back the section before the end of
the inline-asm.
Try:
static void asm_wrapper()
{
    asm volatile (
        ".text\n"
        ".globl " "ctiTrampoline" "\n"
        ".hidden " "ctiTrampoline" "\n"
        "ctiTrampoline" ":" "\n"
        "pushl %ebp" "\n"
        "movl %esp, %ebp" "\n"
        "pushl %esi" "\n"
        "pushl %edi" "\n"
        "pushl %ebx" "\n"
        "subl $0x3c, %esp" "\n"
        "movl $512, %esi" "\n"
        "movl 0x58(%esp), %edi" "\n"
        "call *0x50(%esp)" "\n"
        "addl $0x3c, %esp" "\n"
        "popl %ebx" "\n"
        "popl %edi" "\n"
        "popl %esi" "\n"
        "popl %ebp" "\n"
        "ret" "\n"
        ".previous" "\n"
        );
}


  reply	other threads:[~2010-12-27 20:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 20:16 [Bug inline-asm/47071] New: " alex.wabik at gmail dot com
2010-12-27 20:19 ` pinskia at gcc dot gnu.org [this message]
2010-12-27 20:24 ` [Bug inline-asm/47071] " alex.wabik 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=bug-47071-4-YA3yL2WFQm@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).