public inbox for trinity@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: trinity@vger.kernel.org
Subject: Re: Expected 0x
Date: Wed, 3 Jul 2013 17:29:41 -0400	[thread overview]
Message-ID: <20130703212941.GA26512@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1307031701440.14644@vincent-weaver-1.um.maine.edu>

On Wed, Jul 03, 2013 at 05:07:38PM -0400, Vince Weaver wrote:
 > 
 > The following patch should properly handle decimal values in
 >    /sys/bus/event_source/devices/cpu/events/
 > files.

applied and pushed. thanks.

 > Feel free to run lindent on the whole perf_event_open.c sometime.

maybe next week ;)

btw, here's something curious that llvm finds when you build trinity with clang.
I'm not sure if this is a real problem, or a bug in the compiler, but you
might want to take a look anyway:

syscalls/perf_event_open.c:66:19: warning: Assigned value is garbage or undefined
                format_string[i]=string[i];
                                ^~~~~~~~~~
syscalls/perf_event_open.c:159:12: warning: Assigned value is garbage or undefined
                        field[i]=value[ptr];
                                ^~~~~~~~~~~

In case you're not setup for llvm, I've put the decision trees it generated at
http://codemonkey.org.uk/junk/1.html
http://codemonkey.org.uk/junk/2.html

It may be that some of those combinations it took will never happen, but
I'd like to know for sure. (and if possible somehow silence the warnings
as long as it doesn't ugly stuff up too much)

	Dave

  reply	other threads:[~2013-07-03 21:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 18:21 Expected 0x Dave Jones
2013-07-03 18:43 ` Vince Weaver
2013-07-04  2:42   ` Michael Ellerman
2013-07-04  3:07     ` Vince Weaver
2013-07-04  5:10       ` Michael Ellerman
2013-07-03 21:07 ` Vince Weaver
2013-07-03 21:29   ` Dave Jones [this message]
2013-07-04  3:19     ` Vince Weaver
2013-07-04  4:28       ` Vince Weaver

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=20130703212941.GA26512@redhat.com \
    --to=davej@redhat.com \
    --cc=trinity@vger.kernel.org \
    --cc=vincent.weaver@maine.edu \
    /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