public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/65766] gFortran Compiler SEGFAULTING on compiling simple program Date: Wed, 15 Apr 2015 01:52:00 -0000 [thread overview] Message-ID: <bug-65766-4-lWr3M7EB6i@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65766-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65766 Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2015-04-15 CC| |jvdelisle at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> --- The problem is related to these lines: --- snip --- str%elems(1:) = charvar(1:) --- snip --- charvar(1:) = str%elems(1:) --- snip --- On my system with trunk I get: $ gfc 7.f90 f951: out of memory allocating 26154014304 bytes after a total of 569344 bytes I have ulimits set ... to infinity and beyond!
next prev parent reply other threads:[~2015-04-15 1:52 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-15 0:19 [Bug fortran/65766] New: " giorgianb at gmail dot com 2015-04-15 1:52 ` jvdelisle at gcc dot gnu.org [this message] 2015-07-28 8:26 ` [Bug fortran/65766] " t56xjcu6dh at snkmail dot com 2015-07-28 8:38 ` t56xjcu6dh at snkmail dot com 2015-07-30 12:11 ` dominiq at lps dot ens.fr 2015-09-10 10:00 ` dominiq at lps dot ens.fr 2015-09-10 10:01 ` dominiq at lps dot ens.fr 2015-09-10 10:04 ` dominiq at lps dot ens.fr 2015-10-06 23:47 ` lkrupp at gcc dot gnu.org 2015-10-07 0:14 ` lkrupp at gcc dot gnu.org 2015-10-07 7:47 ` dominiq at lps dot ens.fr 2015-10-07 9:30 ` louis.krupp at zoho dot com
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-65766-4-lWr3M7EB6i@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).