From: fche@redhat.com (Frank Ch. Eigler)
To: ananth@in.ibm.com
Cc: systemtap@sources.redhat.com
Subject: Re: Warnings without -Wno-unused
Date: Thu, 09 Mar 2006 14:09:00 -0000 [thread overview]
Message-ID: <y0mzmjzbtgy.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20060308102702.GA8502@in.ibm.com>
ananth wrote:
> [without -Wno-unused ...]
I agree that we should not need that flag.
> /tmp/stapW5pqzA/stap_2958.c:1279: warning: label unlock_ defined but not used
> /tmp/stapW5pqzA/stap_2958.c:1382: warning: label unlock_ defined but not used
> /tmp/stapW5pqzA/stap_2958.c:1480: warning: unused variable probe_point
I will fix these.
Martin will need to fix these. They look familiar: I suspect he added
the "-Wno-unused" flag to buildrun.cxx back last summer precisely
because he didn't like my hack in the translator to emit dummy
references to these symbols.
> /usr/local/share/systemtap/runtime/transport/transport.c:26: warning: _stp_dpid defined but not used
> /usr/local/share/systemtap/runtime/transport/transport.c:51: warning: _stp_streaming defined but not used
> /usr/local/share/systemtap/runtime/io.c:161: warning: _stp_dbug defined but not used
> /usr/local/share/systemtap/runtime/print.c:160: warning: next_fmt defined but
- FChE
prev parent reply other threads:[~2006-03-09 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 10:27 Ananth N Mavinakayanahalli
2006-03-09 14:09 ` Frank Ch. Eigler [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=y0mzmjzbtgy.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ananth@in.ibm.com \
--cc=systemtap@sources.redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).