From: Simon Marchi <simon.marchi@polymtl.ca>
To: Pedro Alves <palves@redhat.com>
Cc: Weimin Pan <weimin.pan@oracle.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] break gdb build on 32-bit host with ADI support
Date: Fri, 25 Aug 2017 10:33:00 -0000 [thread overview]
Message-ID: <b16bc71dd3f239ce08a377da547b9ea2@polymtl.ca> (raw)
In-Reply-To: <e5172ff5-d369-91b3-c144-a8eabbab39d3@redhat.com>
On 2017-08-25 12:18, Pedro Alves wrote:
> $subject should be "unbreak", I hope. :-)
>
> On 08/25/2017 02:33 AM, Weimin Pan wrote:
>
>> @@ -240,7 +242,7 @@ adi_normalize_address (CORE_ADDR addr)
>> adi_stat_t ast = get_adi_info (ptid_get_pid (inferior_ptid));
>>
>> if (ast.nbits)
>> - return ((CORE_ADDR)(((long)addr << ast.nbits) >> ast.nbits));
>> + return (addr & ((1 << ast.nbits) - 1)) ^ (addr & (-1 >>
>> ast.nbits));
>
> How did you test this? Doesn't look right to me.
> Also, "-1 >>" is still an implementation-defined signed
> right shift.
>
> I _think_ this is what you want:
>
> /* Clear upper bits. */
> addr &= ((uint64_t) -1) >> ast.nbits;
>
> /* Sign extend. */
> CORE_ADDR signbit = (uint64_t) 1 << (64 - ast.nbits - 1);
> return (addr ^ signbit) - signbit;
>
> I.e., with ast.nbits == 4:
>
> before: ffffffffffffffff
> after: ffffffffffffffff
>
> before: f7ffffffffffffff
> after: 07ffffffffffffff
Since it's not trivial, I would suggest putting this operation in its
own function and adding a unit-test for it.
Simon
next prev parent reply other threads:[~2017-08-25 10:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 1:44 Weimin Pan
2017-08-25 10:18 ` Pedro Alves
2017-08-25 10:33 ` Simon Marchi [this message]
2017-08-25 10:44 ` Pedro Alves
2017-08-25 17:43 ` Wei-min Pan
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=b16bc71dd3f239ce08a377da547b9ea2@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=weimin.pan@oracle.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