From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] subtracting pointers on amd64 6c
Date: Tue, 5 Jan 2016 10:28:14 +0000 [thread overview]
Message-ID: <CAOw7k5jXYm_Ynn6pfnaTuyHPVbgkjGBQcgT6bjwQZG1TG8d4XA@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5h2J25XBe3_+m6PiyzuS_yzwEx0dncB5STTFomf3DBtGg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
On 5 January 2016 at 10:15, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
> 2) if a pointer subtraction has to yield a long, why dont we cast *after*
>> the division?
>>
>
> that would be certainly be better.
>
since 6c is more commonly used now, and there's more interest or need, it's
probably best just to introduce
the difference type and change the result type. it's the same thing with
usize.
i'll see if i can add some code to check for mismatches automatically.
there are usable ANSI formats for the difference and sizeof types.
[-- Attachment #2: Type: text/html, Size: 1243 bytes --]
next prev parent reply other threads:[~2016-01-05 10:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 6:36 cinap_lenrek
2016-01-05 7:53 ` cinap_lenrek
2016-01-05 10:17 ` Charles Forsyth
2016-01-05 10:15 ` Charles Forsyth
2016-01-05 10:28 ` Charles Forsyth [this message]
2016-01-05 19:01 ` Devon H. O'Dell
2016-01-05 19:46 ` Charles Forsyth
2016-01-05 20:40 ` erik quanstrom
2016-01-05 21:53 ` Devon H. O'Dell
2016-01-05 23:27 ` erik quanstrom
2016-01-05 23:37 ` Dave Eckhardt
2016-01-05 21:03 ` erik quanstrom
2016-01-05 22:32 ` cinap_lenrek
2016-01-05 22:57 ` Devon H. O'Dell
2016-01-05 23:17 ` Devon H. O'Dell
2016-01-05 23:14 ` erik quanstrom
2016-01-06 6:58 ` cinap_lenrek
2016-01-06 19:10 ` erik quanstrom
2016-01-07 1:08 ` cinap_lenrek
2016-01-08 22:23 ` erik quanstrom
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=CAOw7k5jXYm_Ynn6pfnaTuyHPVbgkjGBQcgT6bjwQZG1TG8d4XA@mail.gmail.com \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).