From: pinskia@gmail.com
To: David Blaikie <dblaikie@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Eric Christopher <echristo@gmail.com>,
Doug Evans <dje@google.com>
Subject: Re: [patch] Fix unused static symbols so they're not dropped by clang
Date: Fri, 11 Apr 2014 07:03:00 -0000 [thread overview]
Message-ID: <72F37201-EB97-4175-B915-F1D4F094F80D@gmail.com> (raw)
In-Reply-To: <CAENS6Es8jHe=xp1Ca0WiZ2dg2JNqJ5JYLP89CCBGWWqPQ20rrQ@mail.gmail.com>
> On Apr 10, 2014, at 11:51 PM, David Blaikie <dblaikie@gmail.com> wrote:
>
> Several tests used file-static functions and variables that were not
> referenced by the code. Even at -O0, clang omits these entities at the
> frontend so the tests fail.
I think clang should change here rather than the testsuite of gdb. Unused static functions make sense to be kept around at -O0 for debugging reasons.
Thanks,
Andrew
>
> Since it doesn't look like these tests needed this functionality for
> what they were testing, I've modified the variables/functions to
> either be non-static, or marked them with __attribute__((used)).
>
> If it's preferred that I use the attribute more pervasively, rather
> than just making the entities non-static, I can provide a patch for
> that (or some other preferred solution). There's certainly precedent
> for both (non-static entities and __attribute__((used)) in the
> testsuite already and much more of the former than the latter).
>
> I have commit-after-review access, so just looking for sign-off here.
>
> Thanks,
> - David
> <unused.diff>
next prev parent reply other threads:[~2014-04-11 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 6:51 David Blaikie
2014-04-11 7:03 ` pinskia [this message]
2014-04-11 18:23 ` Doug Evans
2014-04-11 19:32 ` Doug Evans
2014-04-11 20:16 ` David Blaikie
2014-04-11 20:17 ` David Blaikie
2014-04-12 4:00 ` Andrew Pinski
2014-04-13 7:11 ` David Blaikie
2014-04-14 22:56 ` Doug Evans
2014-04-15 3:24 ` David Blaikie
2014-04-23 21:50 ` Doug Evans
2014-04-25 5:36 ` David Blaikie
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=72F37201-EB97-4175-B915-F1D4F094F80D@gmail.com \
--to=pinskia@gmail.com \
--cc=dblaikie@gmail.com \
--cc=dje@google.com \
--cc=echristo@gmail.com \
--cc=gdb-patches@sourceware.org \
/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