[LLVMbugs] [Bug 705] NEW: bizarre llvm-gcc behaviour (followup of llvm-g++ bug)

bugzilla-daemon at cs.uiuc.edu bugzilla-daemon at cs.uiuc.edu
Tue Feb 7 05:30:31 PST 2006


http://llvm.cs.uiuc.edu/bugs/show_bug.cgi?id=705

           Summary: bizarre llvm-gcc behaviour (followup of llvm-g++ bug)
           Product: libraries
           Version: trunk
          Platform: Macintosh
        OS/Version: MacOS X
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Backend: PowerPC
        AssignedTo: unassignedbugs at nondot.org
        ReportedBy: hp48gx at gmail.com


Hi, some time ago I submitted a bug about llvm-g++.
I enclose again the details below, since I don't have bug# any more.

I downloaded the full cvs version of llvm and llvm-gcc, and compiled both.
Now both llvm-gcc and llvm-g++ compile fine, they give slightly different results (file size differs, but I 
was told that one links against macosx std c library and one against its own library).

However now the compiler behaves strangely: to compile the hello.cpp below, the cpu goes 100% for 
say 10 seconds. Is that normal?

g++ takes (say) less than 1 second.






PowerBookG4:/llvm/test mycroft$ llvm-gcc hello.cpp 
PowerBookG4:/llvm/test mycroft$ ls -l
total 440
-rwxr-xr-x   1 mycroft  admin      64 Jan 12 00:03 a.out
-rwxr-xr-x   1 mycroft  admin  216923 Jan 12 00:03 a.out.bc
-rw-r--r--   1 mycroft  admin      95 Jan 12 00:00 hello.cpp

PowerBookG4:/llvm/test mycroft$ ./a.out
hello world

PowerBookG4:/llvm/test mycroft$ rm a.*   
PowerBookG4:/llvm/test mycroft$ llvm-g++ hello.cpp 
PowerBookG4:/llvm/test mycroft$ ls -l
total 112
-rwxr-xr-x   1 mycroft  admin     64 Jan 12 00:04 a.out
-rwxr-xr-x   1 mycroft  admin  47320 Jan 12 00:04 a.out.bc
-rw-r--r--   1 mycroft  admin     95 Jan 12 00:00 hello.cpp
PowerBookG4:/llvm/test mycroft$ ./a.out
Segmentation fault
PowerBookG4:/llvm/test mycroft$ cat hello.cpp 
#include <iostream>

int main() 
{
     std::cout << "hello world\n";
     return 0;
}



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the llvm-bugs mailing list