public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/63303] Pointer subtraction is broken when using -fsanitize=undefined Date: Fri, 19 Sep 2014 16:21:00 -0000 [thread overview] Message-ID: <bug-63303-4-01guvXc6HW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63303 --- Comment #7 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- Yes, I consider it a bug in malloc that it produces objects 2GB or more in size on 32-bit systems (because of the one-past-end address, the largest size that can't produce undefined behavior in the user program is 2GB minus one byte). Unfortunately I expect some 32-bit applications rely on such large allocations, so if we changed malloc (please report a bug to glibc Bugzilla) we'd need a way (feature test macro?) for people to continue to build programs to use the old malloc, as well as to avoid breaking existing binaries.
next prev parent reply other threads:[~2014-09-19 16:21 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-19 1:42 [Bug c/63303] New: " mikulas at artax dot karlin.mff.cuni.cz 2014-09-19 7:26 ` [Bug c/63303] " jakub at gcc dot gnu.org 2014-09-19 13:38 ` mikulas at artax dot karlin.mff.cuni.cz 2014-09-19 13:47 ` jakub at gcc dot gnu.org 2014-09-19 15:50 ` mikulas at artax dot karlin.mff.cuni.cz 2014-09-19 15:57 ` jakub at gcc dot gnu.org 2014-09-19 16:15 ` mikulas at artax dot karlin.mff.cuni.cz 2014-09-19 16:21 ` joseph at codesourcery dot com [this message] 2014-09-19 16:22 ` jakub at gcc dot gnu.org 2014-09-19 16:29 ` mikulas at artax dot karlin.mff.cuni.cz 2014-09-22 7:42 ` rguenth at gcc dot gnu.org 2014-09-22 14:31 ` mikulas at artax dot karlin.mff.cuni.cz 2015-10-19 11:03 ` rguenth 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-63303-4-01guvXc6HW@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).