mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH] remove stray .end directives
Date: Tue, 2 Jul 2019 19:53:53 +0200	[thread overview]
Message-ID: <20190702175353.GD22788@voyager> (raw)
In-Reply-To: <20190702165841.GZ1506@brightrain.aerifal.cx>

On Tue, Jul 02, 2019 at 12:58:41PM -0400, Rich Felker wrote:
> On Tue, Jul 02, 2019 at 01:09:46PM +0000, Song Fangrui wrote:
> > diff --git a/src/ldso/powerpc64/dlsym.s b/src/ldso/powerpc64/dlsym.s
> > index 7eb691d9..a14715fd 100644
> > --- a/src/ldso/powerpc64/dlsym.s
> > +++ b/src/ldso/powerpc64/dlsym.s
> > @@ -8,5 +8,4 @@ dlsym:
> >  	.localentry dlsym,.-dlsym
> >  	mflr    5                      # The return address is arg3.
> >  	b       __dlsym
> > -	.end    dlsym
> >  	.size   dlsym, .-dlsym
>
> This sounds right. Before I remove this, anyone have any idea what the
> purpose of these was to begin with?
>
> Rich

I can't tell you the purpose, but I can tell you the effect: This
directive ends assembly parsing. Therefore the .size directive below
them was never in effect before (if the documentation is to be trusted).
Dunno if that has any apparent effect though (besides the output of
objdump).

The PPC64 file was added in one go by Bobby Bingham in 2016. I guess the
line there is for consistency with PPC32. The PPC32 file was added in
2012 by rofl0r, though the blame also shows one Richard Pennington (not
the log, though). Weird. Anyway, the log message is also not very
enlightening. I can only assume the line was added in error. That, or
the .size directive. Together they make no sense.

Ciao,
Markus


  reply	other threads:[~2019-07-02 17:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-02 13:09 Song Fangrui
2019-07-02 16:58 ` Rich Felker
2019-07-02 17:53   ` Markus Wichmann [this message]
2019-07-02 21:03     ` Rich Felker
2019-07-03  2:21       ` Fangrui Song

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=20190702175353.GD22788@voyager \
    --to=nullplan@gmx.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).