mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Abdoulaye Walsimou Gaye <awg@embtoolkit.org>
To: musl@lists.openwall.com
Subject: Re: build with clang-3.4 warnings report
Date: Mon, 07 Apr 2014 21:40:52 +0200	[thread overview]
Message-ID: <5342FF44.9060108@embtoolkit.org> (raw)
In-Reply-To: <20140407172334.GC26358@brightrain.aerifal.cx>

On 04/07/2014 07:23 PM, Rich Felker wrote:
> On Mon, Apr 07, 2014 at 11:17:55AM +0000, Oliver Schneider wrote:
>> On 2014-04-05 01:54, Rich Felker wrote:
>>>> src/env/__init_security.c:8:13: warning: function 'dummy' is not needed and will not be emitted [-Wunneeded-internal-declaration]
>>>> static void dummy(void *ent)
>>>>              ^
>>>> 1 warning generated.
>>> This is a bug in the compiler; the function dummy has an externally
>>> visible alias, so it will not be omitted (and if it is actually
>>> omitted, that means the compiler is generating broken output).
>> There is yet another possibility ;)
>>
>> The ccc-analyzer could simply be buggy in this case. Would be
>> interesting to look at the optimized intermediate code whether this gets
>> optimized out. I think it probably doesn't, but who knows.
> At one point it was getting optimized out, which made it impossible to
> build musl with clang, so I think this was fixed and it's just a
> residual bug in the warning generation.
>
>> The dangling else warnings could also be resolved by simply adding
>> braces. It doesn't add to the code size, and the times when developers
>> where paid by LoC are long over (I hope).
>

Hello,
I can confirm that these functions are not optimized out by clang, here is __init_security.o example

     16: 00000000     4 FUNC    LOCAL  DEFAULT    1 dummy
     17: 00000000    24 OBJECT  LOCAL  DEFAULT   22 .L__init_security.pfd
     18: 00000000    10 OBJECT  LOCAL  DEFAULT   23 .L.str
     19: 00000000     0 SECTION LOCAL  DEFAULT   22
     20: 00000000     0 NOTYPE  LOCAL  DEFAULT   22 $d
     21: 00000000     0 SECTION LOCAL  DEFAULT   23
     22: 00000000     0 SECTION LOCAL  DEFAULT   24
     23: 00000000     0 SECTION LOCAL  DEFAULT   25
     24: 00000000     0 SECTION LOCAL  DEFAULT   26
     25: 00000004   208 FUNC    GLOBAL DEFAULT    1 __init_security
     26: 00000000     4 FUNC    WEAK   DEFAULT    1 __init_ssp
     27: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND __syscall
     28: 00000000     0 NOTYPE  GLOBAL DEFAULT  UND __libc


- awg


      reply	other threads:[~2014-04-07 19:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-04 19:59 Abdoulaye Walsimou Gaye
2014-04-04 20:47 ` Rich Felker
2014-04-05  1:06   ` Abdoulaye Walsimou Gaye
2014-04-05  1:54     ` Rich Felker
2014-04-05  9:04       ` Jens Gustedt
2014-04-05  9:31         ` Szabolcs Nagy
2014-04-05 13:07         ` Rich Felker
2014-04-05 14:37           ` Jens Gustedt
2014-04-05 16:35             ` Rich Felker
2014-04-05 22:08               ` Jens Gustedt
2014-04-06  1:57                 ` Rich Felker
2014-04-06 16:37                   ` Jens Gustedt
2014-04-06 16:49                     ` Rich Felker
2014-04-07 11:17       ` Oliver Schneider
2014-04-07 17:23         ` Rich Felker
2014-04-07 19:40           ` Abdoulaye Walsimou Gaye [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=5342FF44.9060108@embtoolkit.org \
    --to=awg@embtoolkit.org \
    --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).