9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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 19:46:35 +0000	[thread overview]
Message-ID: <CAOw7k5ijsx7Y5thQnfrx+F+rcYLBGYBfy3y20aDBOKdci48UHA@mail.gmail.com> (raw)
In-Reply-To: <CAFgOgC9=b6KTHG0qcuLtWgx+1AtMfi-JVKFfjywUq9=JYFuwVA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

On 5 January 2016 at 19:01, Devon H. O'Dell <devon.odell@gmail.com> wrote:

> so given any of the examples in this thread, if you typedef'ed
> ptrdiff_t to long, then the compiler technically isn't actually doing
> anything wrong. whether it is doing something useful is a different
> question.
>

Well, although I knew that was true, I didn't want to push the point because
in practice, people have a right to expect certain reasonable behaviour,
and it's quite reasonable to expect that p+(q-p) yields q if they both point
into the same array that the system agreed to allocate somehow.
It make sense to use 64 bits for the difference, and indeed the code
block that adds the current cast has an if(1 && ...) suggesting an if(0 &&
...
to be inserted instead. It would have been better if I'd simply named it by
enum and
added a comment to explain some of this.

There are some effects on library interfaces that I didn't mention earlier,
but
since 64-bit operation should now be as common as not (allowing for 32-bit
ARM),
it makes sense to update everything to cope with it properly.

[-- Attachment #2: Type: text/html, Size: 1826 bytes --]

  reply	other threads:[~2016-01-05 19:46 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
2016-01-05 19:01     ` Devon H. O'Dell
2016-01-05 19:46       ` Charles Forsyth [this message]
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=CAOw7k5ijsx7Y5thQnfrx+F+rcYLBGYBfy3y20aDBOKdci48UHA@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).