From: Bob Rossi <bob@brasko.net>
To: Nicolas Ouellette <sideshownic@hotmail.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: maximum number of variables?
Date: Tue, 30 Aug 2005 21:08:00 -0000 [thread overview]
Message-ID: <20050830210651.GA1358@white> (raw)
In-Reply-To: <BAY108-F38AC712C2E4B57CDCE983CB3AE0@phx.gbl>
On Tue, Aug 30, 2005 at 05:00:57PM -0400, Nicolas Ouellette wrote:
> Hello
>
> I am presently running a huge code following the hydrodynamical evolution
> of a system (in 2 dimentions). I store the quantities evolving (density,
> velocity, pressure) into large 2-D arrays. Recently, I tried to make my
> 2-D arrays bigger (to study a bigger system) and eventually, I reached a
> certain point where I was getting a "segmentation error". The only thing I
> changed was the size of my arrays.
>
> I deleted a few arrays that were redundant (making my code less user
> friendly), and I found that I could slightly increase the size of my arrays
> until I reached the "segmentation error".
>
> Here are my questions: 1) Is there a maximum number of variables allowed
> when using gcc? (from my experience I am guessing yes) 2) Is there a way to
> increase the number of variables allowed when using gcc?
It sounds like you may have overflowed the stack. Could you try
increasing the stack size? I don't know how to do that though with gcc.
Bob Rossi
next prev parent reply other threads:[~2005-08-30 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-30 21:01 Nicolas Ouellette
2005-08-30 21:08 ` Bob Rossi [this message]
2005-08-30 21:41 ` Nicolas Ouellette
2005-08-30 22:13 ` Lexington Luthor
2005-08-31 1:01 ` Bob Rossi
2005-08-31 4:20 ` Ian Lance Taylor
2005-08-31 9:13 ` Re[2]: " Miguel A. Nuñez
2005-08-31 11:17 ` Bob Rossi
2005-09-01 8:20 ` Re[2]: " Miguel A. Nuñez
2005-08-31 11:19 ` Bob Rossi
2005-08-30 23:01 ` corey taylor
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=20050830210651.GA1358@white \
--to=bob@brasko.net \
--cc=gcc-help@gcc.gnu.org \
--cc=sideshownic@hotmail.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).