From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Cleanup patches
Date: Mon, 6 Jun 2011 20:31:15 +0200 [thread overview]
Message-ID: <20110606183115.GA5512@port70.net> (raw)
In-Reply-To: <20110606173210.GD191@brightrain.aerifal.cx>
* Rich Felker <dalias@aerifal.cx> [2011-06-06 13:32:10 -0400]:
> On Mon, Jun 06, 2011 at 07:13:18PM +0200, Szabolcs Nagy wrote:
> > %.o: $(ARCH)/%.s
> > - $(CC) $(CFLAGS) $(INC) -c -o $@ $<
> > + $(CC) -c -o $@ $<
> >
> > this could be $(AS) -o $@ $<
>
> Is there a reason this is necessary or beneficial?
>
the c compiler may use different asm syntax than you do?
so $(AS) can be something that knows your .s syntax
> > and wcsspn arguments must be const qualified
>
> This is wrong. A non-const-qualified pointer always implicitly
> converts to the const-qualified version.
>
true
> > Subject: [PATCH 6/6] You can't weak alias a static function or variable
> >
> > you can, at least gcc/ld allows it, it just does not make much sense
>
> It does make sense to allow it, but I can see how it might be a little
> more work for the compiler and the compiler might not want to support
> it.
>
what's the difference between
static int f() { stuff(); }
int g() __attribute__((weak, alias("f")));
and
int g() { stuff(); }
?
in the later case local f calls must be replaced by g calls
but other than that is there a difference?
next prev parent reply other threads:[~2011-06-06 18:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 15:40 Igmar Palsenberg
2011-06-06 17:13 ` Szabolcs Nagy
2011-06-06 17:32 ` Rich Felker
2011-06-06 18:31 ` Szabolcs Nagy [this message]
2011-06-06 18:58 ` Rich Felker
2011-06-07 8:44 ` Igmar Palsenberg
2011-06-07 9:06 ` Szabolcs Nagy
2011-06-07 9:08 ` Igmar Palsenberg
2011-06-07 14:51 ` Rich Felker
2011-06-07 15:26 ` Igmar Palsenberg
2011-06-07 15:39 ` Rich Felker
2011-06-07 10:29 ` Igmar Palsenberg
2011-06-06 22:09 ` Rich Felker
2011-06-06 22:13 ` Rich Felker
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=20110606183115.GA5512@port70.net \
--to=nsz@port70.net \
--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).