[LLVMbugs] [Bug 18367] New: crash at some source files with gcc's -O > 0

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Fri Jan 3 05:37:30 PST 2014


            Bug ID: 18367
           Summary: crash at some source files with gcc's -O > 0
           Product: dragonegg
           Version: unspecified
          Hardware: PC
                OS: Windows XP
            Status: NEW
          Severity: normal
          Priority: P
         Component: New Bugs
          Assignee: baldrick at free.fr
          Reporter: mirek.kaim at gmail.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 11810
  --> http://llvm.org/bugs/attachment.cgi?id=11810&action=edit
compilation log

When trying to recompile gcc 4.6.4 with itself with dragonegg enabled (cygwin,
gcc patched to support dll plugins), it crashes at some files - mostly at

gcc configure flags: --enable-shared --enable-static --disable-bootstrap
--with-arch=pentium3 --with-tune=pentium3 --enable-languages=ada,c,c++,fortran
--disable-graphite --enable-lto --enable-threads=posix --disable-win32-registry
--enable-plugin --build=pentium3-pc-cygwin

llvm configure flags: --enable-optimized --disable-assertions --enable-shared
--enable-libffi --enable-ltdl-install --disable-docs --build=pentium3-pc-cygwin

dragonegg compiled with llvm plugins enabled (doesn't seem to make a

llvm and dragonegg 3.4rc3, CFLAGS in the compilation log.

Adding -O0 prevents crash from happening (despite level 3 optimizations enabled
for dragonegg for both ir-optimize and codegen-optimize using CFLAGS), so it is
clearly gcc messing something up. Still, the crash happens regardless of
ir-optimize/codegen-optimize levels for gcc's -O > 0, so if one wants to use
both dragonegg and gcc optimizations, that's something to consider.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20140103/5a2c5e2a/attachment.html>

More information about the llvm-bugs mailing list