From: Florian Weimer <fweimer@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Consensus on unit tests?
Date: Mon, 04 Jul 2016 19:07:00 -0000 [thread overview]
Message-ID: <18522719-c1ac-eb84-1310-95a5f2630252@redhat.com> (raw)
In-Reply-To: <84127229-3bc2-8057-e1be-e4a78889fdbe@redhat.com>
On 07/04/2016 04:27 PM, Carlos O'Donell wrote:
> On 07/01/2016 02:43 AM, Florian Weimer wrote:
>> On 06/25/2016 01:59 AM, Carlos O'Donell wrote:
>>
>>> I would like to remove the superfluous condition and add a unit
>>> test for all the cases that define the way the interface should
>>> behave.
>>>
>>> Since Florian asked for pretty diagrams, I have included them.
>>
>> I can't quote your patch due to the way it is included in the message
>> (inline text after the signature).
>
> I can certainly adjust the way I inline my messages if that helps.
> Out of curiosity, what MUA are you using?
Thunderbird. It usually does not have these problems, but this time,
the patch was included inline after the signature separator. Somehow,
Thunderbird ended up treating it as if format=flowed was specified.
>> What's unclear based on the documentation if the address has to fall
>> in the range covered by the link map (i.e., if there are indeed only
>> three cases, or five). If there is indeed a precondition that the
>> address is in some special range, you should add it to the comment.
>
> There is no precondition that I am aware of. I have clarified the
> new patch to say "loadable segment" where I previously said "segment"
> to make it more clear.
Not even things like âa segment must not cover more than half of the
address spaceâ or âa segment must not cross the middle of the address
spaceâ? Or addr >= l->l_addr?
Intuitively, I would expect that a straight interval comparison as you
wrote it, without any additional checks, would need an additional bit
beyond the word size for it to be correct.
Florian
next prev parent reply other threads:[~2016-07-04 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 23:59 Carlos O'Donell
2016-07-01 6:43 ` Florian Weimer
2016-07-04 14:27 ` Carlos O'Donell
2016-07-04 19:07 ` Florian Weimer [this message]
2016-07-04 20:44 ` Carlos O'Donell
2016-08-15 14:23 ` Florian Weimer
2016-09-03 0:32 ` Roland McGrath
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=18522719-c1ac-eb84-1310-95a5f2630252@redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=libc-alpha@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).