From: agent <agentprog@gmail.com>
To: musl@lists.openwall.com
Subject: Re: build musl with clang
Date: Sat, 25 Aug 2012 11:57:16 +0600 [thread overview]
Message-ID: <5038693C.2020101@gmail.com> (raw)
In-Reply-To: <20120825000917.GK27715@brightrain.aerifal.cx>
25.08.2012 06:09, Rich Felker пишет:
> Here's an idea for a workaround:
>
> void *not_called_malloc(size_t) __asm__("malloc");
> #define malloc not_called_malloc
>
> If that fixes it, it would be an amusing way to present it in the bug
> report.
>
> Rich
that is stilled optimized for a plain malloc call even if i call
not_called_malloc directly and not via a macro. to test the bug i used
the following function:
void *foo(size_t n) {
static char buf[200];
return buf + 10;
}
and that was the way when 'if' was not optimized out. if i use malloc in
foo() it is still wiped out.
as far as i know, optimizations are done not only in clang itself but in
llvm too, so maybe if clang does not notice malloc, llvm does.
next prev parent reply other threads:[~2012-08-25 5:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 7:53 agent
2012-08-23 9:23 ` Szabolcs Nagy
2012-08-23 10:25 ` agent
2012-08-23 12:24 ` Rich Felker
2012-08-23 13:11 ` agent
2012-08-23 13:56 ` John Spencer
2012-08-23 14:42 ` Szabolcs Nagy
2012-08-23 15:12 ` agent
2012-08-23 17:55 ` Rich Felker
2012-08-24 5:58 ` agent
2012-08-24 6:06 ` Rich Felker
2012-08-24 10:37 ` agent
2012-08-24 11:01 ` Szabolcs Nagy
2012-08-24 12:22 ` agent
2012-08-24 12:35 ` Rich Felker
2012-08-24 12:39 ` agent
2012-08-24 14:59 ` Szabolcs Nagy
2012-08-24 17:51 ` Rich Felker
2012-08-24 18:55 ` agent
2012-08-24 19:04 ` Szabolcs Nagy
2012-08-25 0:09 ` Rich Felker
2012-08-25 5:57 ` agent [this message]
2012-08-25 8:03 ` Szabolcs Nagy
2012-08-29 16:21 ` agent
2012-08-29 16:59 ` Rich Felker
2012-08-29 17:50 ` agent
2012-08-24 17:37 ` Luca Barbato
2012-08-24 17:52 ` Rich Felker
2012-08-23 12:24 ` John Spencer
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=5038693C.2020101@gmail.com \
--to=agentprog@gmail.com \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).