From: Ralf Baechle <ralf@linux-mips.org>
To: Sergio Ruiz <quekio@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Linking assembled PIC code with Linux libc library
Date: Mon, 11 Apr 2005 17:09:47 +0100 [thread overview]
Message-ID: <20050411160947.GH7038@linux-mips.org> (raw)
In-Reply-To: <e02bc661050410122733e21927@mail.gmail.com>
On Sun, Apr 10, 2005 at 09:27:58PM +0200, Sergio Ruiz wrote:
> But if I use GCC with my assembler code, and I use a simple 'printf'
> function, the assembler code I get is totally different than the
> original one, so I cant debug it.
Sounds like you're being surprised by the gcc 3.4 optimization where gcc
may replace certain functions such as printf with a whole sequence of
calls to more basic stdio functions?
Ralf
prev parent reply other threads:[~2005-04-11 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 12:09 Linking assembled PIC code with Linux libc library Sergio Ruiz
2005-04-09 13:49 ` Daniel Jacobowitz
[not found] ` <e02bc661050409113820cceae3@mail.gmail.com>
[not found] ` <20050409215140.GA15253@nevyn.them.org>
[not found] ` <e02bc66105041012091afdf306@mail.gmail.com>
2005-04-10 19:27 ` Sergio Ruiz
2005-04-11 16:09 ` Ralf Baechle [this message]
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=20050411160947.GH7038@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=quekio@gmail.com \
/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