From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>, Alexander Shukaev <haroogan@gmail.com>
Cc: 18995@debbugs.gnu.org
Subject: bug#18995: Error: Could not reserve dynamic heap area.
Date: Sat, 08 Nov 2014 20:49:01 +0000 [thread overview]
Message-ID: <545E81BD.8070904@dancol.org> (raw)
In-Reply-To: <83r3xdpiex.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On 11/08/2014 08:05 PM, Eli Zaretskii wrote:
>> Date: Sat, 8 Nov 2014 20:58:02 +0100
>> From: Alexander Shukaev <haroogan@gmail.com>
>> Cc: 18995@debbugs.gnu.org
>>
>> Do you understand why -funroll-loops causes the code to fail to work?
>>
>> Because I cannot. Unless I'm missing something, this sounds like a
>> GCC bug.
>>
>>
>> I've no idea. For that we would have to look into generated assembly code, but
>> I'd rather leave that for compiler professionals to analyze. Would forward it
>> to GCC guys?
>
> It probably does warrant a GCC bug report.
>
>> And how about filtering this flag for good as I asked earlier?
>>
>> CFLAGS := $(filter-out -funroll-loops,$(CFLAGS))
>
> What for? It's a perfectly legitimate compiler switch, and should
> work here as well, I think.
Agreed on not filtering it out.
Alexander, does it help to add explicit debug output (say, fprintf to
stderr) on each iteration of the loop? If not, can you compare the debug
output from the version with -funroll-loops to the one without, to see
whether we're making the same sequence of VirtualAlloc calls? If they're
the same, maybe it's not the loop that's broken, but the address space
layout.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-08 20:49 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 [this message]
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
[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=545E81BD.8070904@dancol.org \
--to=dancol@dancol.org \
--cc=18995@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=haroogan@gmail.com \
/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).