public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dj at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54951] Incorrect pointer handling on 32K boundary Date: Thu, 18 Oct 2012 02:15:00 -0000 [thread overview] Message-ID: <bug-54951-4-qdSbetxR0n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54951-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54951 DJ Delorie <dj at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dj at redhat dot com --- Comment #1 from DJ Delorie <dj at redhat dot com> 2012-10-18 02:14:48 UTC --- This is, unfortunately, the expected behavior for m32c. The m32c has 20-bit pointers but 16-bit math operations, so size_t is 16 bits resulting in many pointer math operations being truncated to 16 bits. So, a COUNT of 0xFFFF may be interpreted as -1 instead of 65536, etc.
next prev parent reply other threads:[~2012-10-18 2:15 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-17 14:37 [Bug c/54951] New: " m.galante at centrosistemi dot it 2012-10-18 2:15 ` dj at redhat dot com [this message] 2012-12-09 2:12 ` [Bug target/54951] " pinskia at gcc dot gnu.org
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=bug-54951-4-qdSbetxR0n@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).