From: Max B <txtmb@yahoo.fr>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: shouldn't gcc use swap space as temp storage??
Date: Thu, 19 Sep 2013 01:25:01 +0100 (BST) [thread overview]
Message-ID: <1379550301.48901.YahooMailNeo@web172202.mail.ir2.yahoo.com> (raw)
In-Reply-To: <1379445730.79703.YahooMailNeo@web172205.mail.ir2.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi All,
See below for executable program.
Shouldn't gcc use swap space as temp storage? Either my machine is set up improperly, or gcc does not (cannot?) access this capability.
It seems to me that programs should be able to access swap memory in these cases, but the behaviour has not been confirmed.
Can someone please confirm or correct me?
Apologies if this is not the correct listserv for the present discussion.
Thanks for any/all help.
Cheers,
Max
/*
* This program segfaults with the *bar array declaration.
*
* I wonder why it does not write the *foo array to swap space
* then use the freed ram to allocate *bar.
*
* I have explored the shell ulimit parameters to no avail.
*
* I have run this as root and in userland with the same outcome.
*
* It seems to be a problem internal to gcc, but may also be a kernel issue.
*
*/
#include <stdio.h>
#include <stdlib.h>
#define NMAX 628757505
int main(int argc,char **argv) {
float *foo,*bar;
foo=calloc(NMAX,sizeof(float));
fprintf(stderr,"%9.3f %9.3f\n",foo[0],foo[1]);
#if 1
bar=calloc(NMAX,sizeof(float));
fprintf(stderr,"%9.3f %9.3f\n",bar[0],bar[1]);
#endif
return
0;
}
[-- Attachment #2: Type: text/html, Size: 4353 bytes --]
next prev parent reply other threads:[~2013-09-19 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:22 does gcc segfault when main memory is overfull? Max B
2013-09-19 0:25 ` Max B [this message]
2013-09-19 4:14 ` shouldn't gcc use swap space as temp storage?? Vladimir Murzin
2013-09-21 3:13 ` Max B
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=1379550301.48901.YahooMailNeo@web172202.mail.ir2.yahoo.com \
--to=txtmb@yahoo.fr \
--cc=linux-mm@kvack.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox