From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: cgen@sources.redhat.com
Subject: bitrange-overlap: Handle lsb0
Date: Mon, 07 Oct 2002 17:00:00 -0000 [thread overview]
Message-ID: <200210080000.CAA24243@ignucius.axis.se> (raw)
(Question-marks removed to allude subject spam filter that trigs
for some reason -- overseers informed. If you get this twice
this is the resend you should reply to.)
I just committed Doug Evans suggestion (and approval) in
<URL:http://sources.redhat.com/ml/cgen/2002-q2/msg00031.html>,
though I included myself in the ChangeLog entry so some of the
blame for any failure will fall on me. I didn't notice I had
missed committing this patch until its absence caused a local
test-case to fail. Mea culpa.
2002-10-08 Doug Evans <dje@transmeta.com>
Hans-Peter Nilsson <hp@axis.com>
* types.scm (bitrange-overlap?): Handle lsb0?.
Index: types.scm
===================================================================
RCS file: /cvs/src/src/cgen/types.scm,v
retrieving revision 1.1.1.1
diff -p -c -r1.1.1.1 types.scm
*** types.scm 28 Jul 2000 04:11:52 -0000 1.1.1.1
--- types.scm 7 Oct 2002 23:28:29 -0000
***************
*** 241,251 ****
; Return a boolean indicating if two bitranges overlap.
(define (bitrange-overlap? start1 length1 start2 length2 lsb0?)
! ; ??? lsb0?
! (let ((end1 (+ start1 length1))
! (end2 (+ start2 length2)))
! (not (or (<= end1 start2)
! (>= start1 end2))))
)
; Return a boolean indicating if BITPOS is beyond bitrange START,LEN.
--- 241,255 ----
; Return a boolean indicating if two bitranges overlap.
(define (bitrange-overlap? start1 length1 start2 length2 lsb0?)
! (if lsb0?
! (let ((end1 (- start1 length1))
! (end2 (- start2 length2)))
! (and (< end1 start2)
! (> start1 end2)))
! (let ((end1 (+ start1 length1))
! (end2 (+ start2 length2)))
! (and (> end1 start2)
! (< start1 end2))))
)
; Return a boolean indicating if BITPOS is beyond bitrange START,LEN.
brgds, H-P
reply other threads:[~2002-10-08 0:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200210080000.CAA24243@ignucius.axis.se \
--to=hans-peter.nilsson@axis.com \
--cc=cgen@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).