* Array Dimension Question
@ 2001-10-17 8:46 Vanhouten, Chris L
2001-10-17 21:11 ` Frank Schafer
0 siblings, 1 reply; 4+ messages in thread
From: Vanhouten, Chris L @ 2001-10-17 8:46 UTC (permalink / raw)
To: 'gcc-help@gcc.gnu.org'
The g77 compiler doesn't support array's that have more than 8192 elements.
The limit is dependent on the range of an integer (which is platform
dependent). The RedHat 7.1 load that I'm using has the compiler natively
built for i386. I'm trying to rebuild for i686 to take advantage of the
extra bits, such that the range of an integer is expanded. This limitation
is part of the g77 front end, and not the gcc back end. Does anyone know a
way to get around this?
Chris L. VanHouten
Systems Engineer
Trade Studies & Issue Resolution, System Analysis
THAAD Weapon Systems Engineering
Lockheed Martin Space Systems Company-Missiles & Space Operations
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Array Dimension Question
2001-10-17 8:46 Array Dimension Question Vanhouten, Chris L
@ 2001-10-17 21:11 ` Frank Schafer
0 siblings, 0 replies; 4+ messages in thread
From: Frank Schafer @ 2001-10-17 21:11 UTC (permalink / raw)
To: Vanhouten, Chris L; +Cc: 'gcc-help@gcc.gnu.org'
"Vanhouten, Chris L" wrote:
> The g77 compiler doesn't support array's that have more than 8192 elements.
> The limit is dependent on the range of an integer (which is platform
> dependent). The RedHat 7.1 load that I'm using has the compiler natively
> built for i386. I'm trying to rebuild for i686 to take advantage of the
> extra bits, such that the range of an integer is expanded. This limitation
> is part of the g77 front end, and not the gcc back end. Does anyone know a
> way to get around this?
>
> Chris L. VanHouten
> Systems Engineer
> Trade Studies & Issue Resolution, System Analysis
> THAAD Weapon Systems Engineering
> Lockheed Martin Space Systems Company-Missiles & Space Operations
Rebuild with the -march=i686 switch.
Frank
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: Array Dimension Question
2001-10-16 12:55 Vanhouten, Chris L
@ 2001-10-17 0:27 ` Rupert Wood
0 siblings, 0 replies; 4+ messages in thread
From: Rupert Wood @ 2001-10-17 0:27 UTC (permalink / raw)
To: 'Vanhouten, Chris L'; +Cc: gcc-help
Chris L. Vanhouten wrote:
> Is there a way to get around the array size limitation?
Forgive my ignorance - what array size limitation?
If you mean that your OS limits the amount of space you can take from
the stack, you could always dynamically allocate an array on the heap:
malloc() in C, then recast the pointer and free() when you're done, or
new then delete in C++.
Rup.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Array Dimension Question
@ 2001-10-16 12:55 Vanhouten, Chris L
2001-10-17 0:27 ` Rupert Wood
0 siblings, 1 reply; 4+ messages in thread
From: Vanhouten, Chris L @ 2001-10-16 12:55 UTC (permalink / raw)
To: 'gcc-help@gcc.gnu.org'
Is there a way to get around the array size limitation?
Thanks for your assistance.
Chris L. VanHouten
Systems Engineer
Trade Studies & Issue Resolution, System Analysis
THAAD Weapon Systems Engineering
Lockheed Martin Space Systems Company-Missiles & Space Operations
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-10-17 21:11 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-10-17 8:46 Array Dimension Question Vanhouten, Chris L
2001-10-17 21:11 ` Frank Schafer
-- strict thread matches above, loose matches on Subject: below --
2001-10-16 12:55 Vanhouten, Chris L
2001-10-17 0:27 ` Rupert Wood
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).