www.digitalmars.com         C & C++   DMDScript  

D.gnu - [Bug 88] New: -flto option causes internal compiler error

http://bugzilla.gdcproject.org/show_bug.cgi?id=88


           Summary: -flto option causes internal compiler error
    Classification: Unclassified
           Product: GDC
           Version: 4.8.x
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gdc
        AssignedTo: ibuclaw gdcproject.org
        ReportedBy: secondaryaccount web.de


Created attachment 55
  --> http://bugzilla.gdcproject.org/attachment.cgi?id=55
printed stacktrace

I tried to compile with -flto and got an internal compiler error, even for a
very simple example:

file app.d:
import  bar;

void main(string[] args){
    foo();
}

file bar.d:
module bar;

int foo() {
    return 0;
}

gdc -flto app.d bar.d 

(see Attachment for the stacktrace)

The stacktrace in
http://forum.dlang.org/thread/mailman.277.1362743197.14496.d.gnu puremagic.com
seemed to be similar...

If gdc 4.8 does not support LTO or it's a bug in GCC, it may be possible to
print a warning or error message instead of the stacktrace when -flto is passed
to gdc. I guess all given options are read to find the D-specific ones like
-frelease, so perhaps it's not much work to implement a check for -flto (?) 

OS: Ubuntu 12.04
Compiler Version: gdc -v
Es werden eingebaute Spezifikationen verwendet.
COLLECT_GCC=gdc
COLLECT_LTO_WRAPPER=/opt/gdc/libexec/gcc/i686-pc-linux-gnu/4.8.2/lto-wrapper
Ziel: i686-pc-linux-gnu
Konfiguriert mit: ../gcc-4.8.2/configure --enable-languages=d
--enable-checking=release --prefix=/opt/gdc
--with-bugurl=http://gdcproject.org/bugzilla
Thread-Modell: posix
gcc-Version 4.8.2 (GCC)


PS: in the README.md and on github the link to the wiki is still
http://gdcproject.org/wiki. Could you update it to http://wiki.dlang.org/GDC ?
The old link is not found anymore...

-- 
Configure bugmail: http://bugzilla.gdcproject.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
Dec 31 2013