public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/53452] New: large array problem x86_64
@ 2012-05-22 13:04 peter.faasse at nlr dot nl
  2012-05-22 13:07 ` [Bug c/53452] " peter.faasse at nlr dot nl
  2012-05-22 13:41 ` rguenth at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: peter.faasse at nlr dot nl @ 2012-05-22 13:04 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53452

             Bug #: 53452
           Summary: large array problem x86_64
    Classification: Unclassified
           Product: gcc
           Version: 4.5.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: peter.faasse@nlr.nl


Created attachment 27475
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27475
per-request, the .i file, command-line file will follow

The following very simple program:
--------------------------------------------------------
int main(int argc, char *argv[])
{
    //
    int ttt[1073741824];    // fails --> segmentation fault
    //int ttt[1048576];    // ok
    //
    return 0;
    //
}
--------------------------------------------------------
segfaults when an array of 1Gig ints is declared. 
In gdb that shows up as: 
--------------------------------------------------------
(gdb) b main
Breakpoint 1 at 0x4004d0: file test.c, line 7.
(gdb) r
Starting program: /home/prf/z08/ALL/DSC/test/test 

Program received signal SIGSEGV, Segmentation fault.
0x00000000004004bc in main (argc=Cannot access memory at address 0xfffeffffc99c
) at test.c:2
2       {
--------------------------------------------------------


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug c/53452] large array problem x86_64
  2012-05-22 13:04 [Bug c/53452] New: large array problem x86_64 peter.faasse at nlr dot nl
@ 2012-05-22 13:07 ` peter.faasse at nlr dot nl
  2012-05-22 13:41 ` rguenth at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: peter.faasse at nlr dot nl @ 2012-05-22 13:07 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53452

--- Comment #1 from Peter Faasse <peter.faasse at nlr dot nl> 2012-05-22 13:03:59 UTC ---
Created attachment 27476
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27476
gcc -v  etcetera version of gcc

Distribution is Slackware-64 13.37


^ permalink raw reply	[flat|nested] 3+ messages in thread
* [Bug c/53452] large array problem x86_64
  2012-05-22 13:04 [Bug c/53452] New: large array problem x86_64 peter.faasse at nlr dot nl
  2012-05-22 13:07 ` [Bug c/53452] " peter.faasse at nlr dot nl
@ 2012-05-22 13:41 ` rguenth at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: rguenth at gcc dot gnu.org @ 2012-05-22 13:41 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53452

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-22 13:27:16 UTC ---
Increase your stack limit - 'ulimit -s unlimited' is your friend.


^ permalink raw reply	[flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-05-22 13:27 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-05-22 13:04 [Bug c/53452] New: large array problem x86_64 peter.faasse at nlr dot nl
2012-05-22 13:07 ` [Bug c/53452] " peter.faasse at nlr dot nl
2012-05-22 13:41 ` rguenth at gcc dot gnu.org

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).