unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 18995@debbugs.gnu.org, haroogan@gmail.com
Subject: bug#18995: Error: Could not reserve dynamic heap area.
Date: Sun, 09 Nov 2014 18:47:00 +0200	[thread overview]
Message-ID: <834mu8pbi3.fsf@gnu.org> (raw)
In-Reply-To: <87vbmoqqua.fsf@igel.home>

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: eliz@gnu.org,  haroogan@gmail.com
> Date: Sun, 09 Nov 2014 17:30:21 +0100
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Given that, it is justified for GCC to give us what we deserve, i.e. a
> > loop "unrolled" by executing its body only once.  I present the
> > disassembly below, for the curious, and it's clear that there's no
> > loop there, and also the value of 'size' is never tested at all, since
> > GCC decided that the condition 'size > 0x00100000' is always true.
> 
> But if you replace 'size > 0x00100000' with true, you get a loop that is
> conditionalized by '!ptr', which depends on the execution of the loop
> body.  Why would it be correct to execute the loop only once,
> unconditionally?

Feel free to report this as a GCC bug, if you think that's what it is.
All I can tell is that the same behavior is present in 3 different GCC
releases from 3 different major versions.

In any case, I think the original code had a subtle bug, in that the
comparison of 'size' didn't do what the author intended.





  reply	other threads:[~2014-11-09 16:47 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 [this message]
     [not found]                       ` <545F94E4.5060102@dancol.org>
2014-11-09 16:30                         ` Alexander Shukaev
     [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=834mu8pbi3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18995@debbugs.gnu.org \
    --cc=haroogan@gmail.com \
    --cc=schwab@linux-m68k.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).