unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: "Mike Gran" <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: GC Warning related to large mem block allocation - Help needed
Date: Sat, 30 Dec 2017 21:38:26 -0200	[thread overview]
Message-ID: <20171230213826.67b17aae@capac> (raw)
In-Reply-To: <20171230051051.GA10643@joshua.dnsalias.com>

[-- Attachment #1: Type: text/plain, Size: 2550 bytes --]

Hi Mike,

> If all you are doing is trying to get Guile not to issue warnings about big
> allocations, I think all you need to do is put -DGC_IGNORE_WARN in the
> CFLAGS when you build Guile.

Thanks for the suggestion, but it does not work. If I trust guile (gcc) to use an
exported CFLAGS env variable:

	export CFLAGS="-O3 -DGC_IGNORE_WARN"
	[ which is properly listed in the config.log after configure...

and if this flag is 'correct', it appeared to work at first glance:

	scheme@(guile-user)> ,use (srfi srfi-4)
	scheme@(guile-user)>  (for-each (lambda (i) (make-f32vector 100000000)) (iota 100))
	[ no warnings here

but a more expensive task triggers these warnings still

scheme@(guile-user)> ,time (quasep caso-9 '1mm)
 init...  GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
kernels... GC Warning: Repeated allocation of very large block (appr. size 775237632):
	May lead to memory leak and poor performance.
small pellets... GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
grip layer... GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
micro pellets... GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
gripped kernels... GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
none gripped kernels... GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.
quase particles... GC Warning: Repeated allocation of very large block (appr. size 775012352):
	May lead to memory leak and poor performance.

$1 = ((13755 14086 3 (#f32(255.0 255.0 255.0 255.0 255.0 255.0 255.0 # # ...) ...)) # ...)
;; 300.318682s real time, 369.596406s run time.  5.252115s spent in GC.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2017-12-30 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-30  1:48 GC Warning related to large mem block allocation - Help needed David Pirotte
2017-12-30  2:35 ` David Pirotte
2017-12-30  4:05 ` David Pirotte
2017-12-30  5:10   ` Mike Gran
2017-12-30 23:38     ` David Pirotte [this message]
2017-12-31 13:22       ` David Pirotte
2018-01-01 14:11         ` Freja Nordsiek
2018-01-01 22:05           ` Daniel Llorens

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/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171230213826.67b17aae@capac \
    --to=david@altosw.be \
    --cc=guile-devel@gnu.org \
    --cc=spk121@yahoo.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.
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).