From: Roland McGrath <roland@redhat.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Mike Mason <mmlnx@us.ibm.com>, systemtap@sources.redhat.com
Subject: Re: Problem with 32-bit negative return values
Date: Tue, 10 Oct 2006 18:28:00 -0000 [thread overview]
Message-ID: <20061010182831.CA3B7180066@magilla.sf.frob.com> (raw)
In-Reply-To: Frank Ch. Eigler's message of Tuesday, 10 October 2006 13:51:59 -0400 <20061010175159.GH14473@redhat.com>
> It could easily be a typing/sign-extension bug in the loc2c-related
> code. Could you check the generated C code (-p3; look for the
> _dwarf_tvar_get function)?
All loc2c-generated fetches use unsigned types of the target object size,
i.e. uint32_t here. loc2c just fetches the bits.
Your general expression code that uses the fetched value should cast
appropriately for the signedness and size you want to calculate with.
next prev parent reply other threads:[~2006-10-10 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <452BD98F.8050602@us.ibm.com>
2006-10-10 17:52 ` Frank Ch. Eigler
2006-10-10 18:28 ` Roland McGrath [this message]
2006-10-10 20:25 ` Frank Ch. Eigler
2006-10-10 20:41 ` Mike Mason
2006-10-07 21:23 Mike Mason
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=20061010182831.CA3B7180066@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=fche@redhat.com \
--cc=mmlnx@us.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).