public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug sanitizer/94191] New: ubsan bootstrap memory hog with -enable-checking=rtl
@ 2020-03-16  9:50 zhroma at gcc dot gnu.org
  2020-03-16  9:57 ` [Bug sanitizer/94191] " jakub at gcc dot gnu.org
  2020-03-16 11:00 ` rguenth at gcc dot gnu.org
  0 siblings, 2 replies; 3+ messages in thread
From: zhroma at gcc dot gnu.org @ 2020-03-16  9:50 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 94191
           Summary: ubsan bootstrap memory hog with -enable-checking=rtl
           Product: gcc
           Version: 9.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhroma at gcc dot gnu.org
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

On 64Gb RAM x86_64 box using 9.3 sources and running:
<src>/configure --enable-languages=c,c++ --with-build-config=bootstrap-ubsan
--enable-checking=rtl;  make

During stage2 insn-extract.c compilation was stopped by OOM killer.  It really
wants 60+ Gb of memory.

--
Yeah, it's a bit crazy checking options and not sure we have to bother about
it.

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

* [Bug sanitizer/94191] ubsan bootstrap memory hog with -enable-checking=rtl
  2020-03-16  9:50 [Bug sanitizer/94191] New: ubsan bootstrap memory hog with -enable-checking=rtl zhroma at gcc dot gnu.org
@ 2020-03-16  9:57 ` jakub at gcc dot gnu.org
  2020-03-16 11:00 ` rguenth at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: jakub at gcc dot gnu.org @ 2020-03-16  9:57 UTC (permalink / raw)
  To: gcc-bugs

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

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Don't do it or buy enough memory.
RTL checking alone already creates lots of basic blocks due to all the checks
it performs (in the code the compiler is compiling) and ubsan as well (in the
instrumentation it adds for it), and when you compile the huge auto-generated
files, it is costly.

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

* [Bug sanitizer/94191] ubsan bootstrap memory hog with -enable-checking=rtl
  2020-03-16  9:50 [Bug sanitizer/94191] New: ubsan bootstrap memory hog with -enable-checking=rtl zhroma at gcc dot gnu.org
  2020-03-16  9:57 ` [Bug sanitizer/94191] " jakub at gcc dot gnu.org
@ 2020-03-16 11:00 ` rguenth at gcc dot gnu.org
  1 sibling, 0 replies; 3+ messages in thread
From: rguenth at gcc dot gnu.org @ 2020-03-16 11:00 UTC (permalink / raw)
  To: gcc-bugs

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |memory-hog

--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I suggest to use -O1, that should help.

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

end of thread, other threads:[~2020-03-16 11:00 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-16  9:50 [Bug sanitizer/94191] New: ubsan bootstrap memory hog with -enable-checking=rtl zhroma at gcc dot gnu.org
2020-03-16  9:57 ` [Bug sanitizer/94191] " jakub at gcc dot gnu.org
2020-03-16 11:00 ` 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).