From: Alexander Shukaev <haroogan@gmail.com>
To: Daniel Colascione <dancol@dancol.org>
Cc: 18995-done@debbugs.gnu.org
Subject: bug#18995: Error: Could not reserve dynamic heap area.
Date: Sun, 9 Nov 2014 17:30:38 +0100 [thread overview]
Message-ID: <CAKu-7WymBfLwuDeKC3UAL+tGsSSBUTdmwiEvrRW7NygJa3DH8w@mail.gmail.com> (raw)
In-Reply-To: <545F94E4.5060102@dancol.org>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
>
> How can this be a bug in our code? Wraparound of unsigned values is
> well-defined.
True, it is well-defined, but it was not intended for sure, hence it's a
100% bug. Eli's term of "undefined behavior" was an exaggeration I think.
I don't think the compiler is justified in making this optimization.
> Since when is an infinite loop undefined behavior? GCC has no right to
> alter program semantics in this case, loop unrolling or no.
I would agree here, throwing out wrapped loop is just too much even though
such loop was unintended. GCC should have either left it alone since it is
infinite or make a warning. I think this case is still worth showing to GCC
developers.
[-- Attachment #2: Type: text/html, Size: 1227 bytes --]
next prev parent reply other threads:[~2014-11-09 16:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 15:22 bug#18995: Error: Could not reserve dynamic heap area Alexander Shukaev
2014-11-08 17:29 ` Eli Zaretskii
2014-11-08 18:17 ` Alexander Shukaev
2014-11-08 18:30 ` Eli Zaretskii
2014-11-08 18:40 ` Alexander Shukaev
2014-11-08 18:57 ` Eli Zaretskii
2014-11-08 19:16 ` Alexander Shukaev
2014-11-08 19:50 ` Eli Zaretskii
2014-11-08 19:58 ` Alexander Shukaev
2014-11-08 20:05 ` Eli Zaretskii
2014-11-08 20:49 ` Daniel Colascione
2014-11-09 16:12 ` Eli Zaretskii
2014-11-09 16:30 ` Andreas Schwab
2014-11-09 16:47 ` Eli Zaretskii
[not found] ` <545F94E4.5060102@dancol.org>
2014-11-09 16:30 ` Alexander Shukaev [this message]
[not found] ` <837fz4pc4o.fsf@gnu.org>
2014-11-09 16:40 ` Daniel Colascione
2014-11-09 16:35 ` Andreas Schwab
2014-11-09 16:39 ` Alexander Shukaev
2014-11-09 16:49 ` Eli Zaretskii
2014-11-09 16:53 ` Alexander Shukaev
2014-11-09 17:17 ` Eli Zaretskii
2014-11-09 17:14 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKu-7WymBfLwuDeKC3UAL+tGsSSBUTdmwiEvrRW7NygJa3DH8w@mail.gmail.com \
--to=haroogan@gmail.com \
--cc=18995-done@debbugs.gnu.org \
--cc=dancol@dancol.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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).