public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/104227] New: [9/10/11/12 Regression] ICE virtual memory exhausted: Cannot allocate memory
Date: Tue, 25 Jan 2022 18:02:50 +0000	[thread overview]
Message-ID: <bug-104227-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104227

            Bug ID: 104227
           Summary: [9/10/11/12 Regression] ICE virtual memory exhausted:
                    Cannot allocate memory
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
          Assignee: unassigned at gcc dot gnu.org
          Reporter: gscfq@t-online.de
  Target Milestone: ---

Affects versions down to r8, changed between 20190208 and 20190308 :
(follow-up of pr101514)


$ cat z1.f90
program p
   type t
   end type
   type(t) :: x(2)
   print *, transfer(1, x)
end


$ cat z2.f90
program p
   type t
   end type
   type(t) :: x(2)
   x = transfer(1, x)
end


$ gfortran-12-20220123 -c z1.f90
virtual memory exhausted: Cannot allocate memory


$ gfortran-12-20220123 -c z2.f90
GNU MP: Cannot allocate memory (size=8)
f951: internal compiler error: Aborted
mmap: Cannot allocate memory


$ gfortran-12-20220123-chk -c z1.f90   # ulimits set
GNU MP: Cannot allocate memory (size=8)

f951: out of memory allocating 139 bytes after a total of 1494507520 bytes

             reply	other threads:[~2022-01-25 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 18:02 gscfq@t-online.de [this message]
2022-01-25 20:46 ` [Bug fortran/104227] " anlauf at gcc dot gnu.org
2022-01-25 20:57 ` cvs-commit at gcc dot gnu.org
2022-01-25 21:04 ` anlauf at gcc dot gnu.org
2022-01-26  8:16 ` marxin at gcc dot gnu.org
2022-01-26 17:13 ` [Bug fortran/104227] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-01-26 17:56 ` cvs-commit at gcc dot gnu.org
2022-01-26 18:02 ` cvs-commit at gcc dot gnu.org
2022-01-26 18:05 ` anlauf 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-104227-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: 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).