public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "peter.faasse at nlr dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/53452] New: large array problem x86_64 Date: Tue, 22 May 2012 13:04:00 -0000 [thread overview] Message-ID: <bug-53452-4@http.gcc.gnu.org/bugzilla/> (raw) 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 { --------------------------------------------------------
next reply other threads:[~2012-05-22 13:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-22 13:04 peter.faasse at nlr dot nl [this message] 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
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=bug-53452-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).