public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug driver/68038] New: "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted"
@ 2015-10-21  2:31 zackw at panix dot com
  2015-10-21  2:33 ` [Bug driver/68038] " pinskia at gcc dot gnu.org
  2015-10-22 14:40 ` d.u.thibault at bigfoot dot com
  0 siblings, 2 replies; 3+ messages in thread
From: zackw at panix dot com @ 2015-10-21  2:31 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 68038
           Summary: "Internal compiler error: Killed: program cc1" should
                    read "Virtual memory exhausted"
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zackw at panix dot com
  Target Milestone: ---

99+% of the time, when the compiler proper dies on signal 9, it's because we're
on Linux and the out-of-memory killer has killed the compiler proper because it
ate all available RAM.  But the error message you get when this happens
*sounds* like there's a bug in GCC.

I suggest the driver be changed to special-case SIGKILL and print a different
message, along the lines of

   gcc: compilation process (cc1) killed by SIGKILL
   This almost always means your computer does not have enough RAM to
   compile this program.  Try adding swap space or reducing the
   number of concurrent compile jobs.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug driver/68038] "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted"
  2015-10-21  2:31 [Bug driver/68038] New: "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted" zackw at panix dot com
@ 2015-10-21  2:33 ` pinskia at gcc dot gnu.org
  2015-10-22 14:40 ` d.u.thibault at bigfoot dot com
  1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2015-10-21  2:33 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-10-21
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed.


^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Bug driver/68038] "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted"
  2015-10-21  2:31 [Bug driver/68038] New: "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted" zackw at panix dot com
  2015-10-21  2:33 ` [Bug driver/68038] " pinskia at gcc dot gnu.org
@ 2015-10-22 14:40 ` d.u.thibault at bigfoot dot com
  1 sibling, 0 replies; 3+ messages in thread
From: d.u.thibault at bigfoot dot com @ 2015-10-22 14:40 UTC (permalink / raw)
  To: gcc-bugs

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

Daniel U. Thibault <d.u.thibault at bigfoot dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |d.u.thibault at bigfoot dot com

--- Comment #2 from Daniel U. Thibault <d.u.thibault at bigfoot dot com> ---
Confirmed.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-10-22 14:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-21  2:31 [Bug driver/68038] New: "Internal compiler error: Killed: program cc1" should read "Virtual memory exhausted" zackw at panix dot com
2015-10-21  2:33 ` [Bug driver/68038] " pinskia at gcc dot gnu.org
2015-10-22 14:40 ` d.u.thibault at bigfoot dot com

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