thr3ads.net - llvm dev - [LLVMdev] Antw.: 2.0 Pre-release tarballs online [May 2007]

If this information is useful, please help other people find it:
Share via:

Bram Adams

2007-May-18 16:12 UTC

[LLVMdev] Antw.: 2.0 Pre-release tarballs online

Hi,

Op 18-mei-07, om 10:10 heeft Tanya M. Lattner het volgende geschreven:
>> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build  
>> with the header files using uintptr_t (not recognised as a type).  
>> Putting "#include <stdint.h>" in
include/llvm/BasicBlock.h (llvm)
>> and in "include/llvm/ValueSymbolTable.h" (frontend) resolved
this.
>
> Ok. This is now fixed on the release branch. Thanks!
The strange thing is that the configure process defines:

#define HAVE_STDINT_H 1

However, without literally including stdint.h (which should be  
avoided as Reid mentioned) the compilation of AsmWriter.cpp goes  
wrong, although stdint.h, llvm/Support/DataTypes.h and inttypes.h are  
all mentioned in AsmWriter.d:

if g++ -I/home/bram/workspace/svn/aspicere2/trunk/llvm-build/lib/ 
VMCore -I/home/bram/workspace/svn/aspicere2/trunk/llvm/lib/VMCore -I/ 
home/bram/workspace/svn/aspicere2/trunk/llvm-build/include -I/home/ 
bram/workspace/svn/aspicere2/trunk/llvm/include -I/home/bram/ 
workspace/svn/aspicere2/trunk/llvm-build/include -I/home/bram/ 
workspace/svn/aspicere2/trunk/llvm/include  -D_GNU_SOURCE - 
D__STDC_LIMIT_MACROS -g -fno-exceptions -D_DEBUG  -Woverloaded- 
virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused - 
Wno-unused-parameter  -c -MD -MT /home/bram/workspace/svn/aspicere2/ 
trunk/llvm-build/lib/VMCore/Debug/AsmWriter.o -MP -MF /home/bram/ 
workspace/svn/aspicere2/trunk/llvm-build/lib/VMCore/Debug/ 
AsmWriter.LACXXd /home/bram/workspace/svn/aspicere2/trunk/llvm/lib/ 
VMCore/AsmWriter.cpp -o /home/bram/workspace/svn/aspicere2/trunk/llvm- 
build/lib/VMCore/Debug/AsmWriter.o ;\
   then /usr/bin/mv -f "/home/bram/workspace/svn/aspicere2/trunk/llvm- 
build/lib/VMCore/Debug/AsmWriter.LACXXd" "/home/bram/workspace/svn/ 
aspicere2/trunk/llvm-build/lib/VMCore/Debug/AsmWriter.d"; \
   else /usr/bin/rm -f "/home/bram/workspace/svn/aspicere2/trunk/llvm- 
build/lib/VMCore/Debug/AsmWriter.LACXXd"; exit 1; fi
In file included from /home/bram/workspace/svn/aspicere2/trunk/llvm/ 
include/llvm/Function.h:22,
                  from /home/bram/workspace/svn/aspicere2/trunk/llvm/ 
include/llvm/Module.h:17,
                  from /home/bram/workspace/svn/aspicere2/trunk/llvm/ 
include/llvm/Assembly/PrintModulePass.h:22,
                  from /home/bram/workspace/svn/aspicere2/trunk/llvm/ 
lib/VMCore/AsmWriter.cpp:18:
/home/bram/workspace/svn/aspicere2/trunk/llvm/include/llvm/ 
BasicBlock.h: In
    static member function `static unsigned int
    llvm::BasicBlock::getInstListOffset()':
/home/bram/workspace/svn/aspicere2/trunk/llvm/include/llvm/ 
BasicBlock.h:197: error: syntax
    error before `;' token
...

Should -DHAVE_STDINT_H be passed to the above command?
>
>> Also, I got linking errors while linking tblgen (see error.txt).  
>> Any ideas about this?
>
> I'm not really sure whats going on here and I can't reproduce this
> since I don't have your setup. Its probably either an issue with  
> gcc or ld (try upgrading to 2.17.X if possible). If you can try to  
> investigate it further, that would be great. Then file a bug for it.
Problem solved: compiling the 2.0 frontend from source had resulted  
in gcc, g++, ... instead of llvm-gcc, llvm-g++, ... After manually  
renaming them, compilation of LLVM was a breeze and the tests did not  
yield any unexpected failures (see attachment).

Kind regards,

Bram Adams
GH-SEL, INTEC, Ghent University (Belgium)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: x86.log.zip
Type: application/zip
Size: 19787 bytes
Desc: not available
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20070518/d14c6703/attachment.zip>

Reid Spencer

2007-May-18 16:40 UTC

head link

[LLVMdev] Antw.: 2.0 Pre-release tarballs online

Hi Bram,

On Fri, 2007-05-18 at 18:12 +0200, Bram Adams wrote:> Hi,
> 
> Op 18-mei-07, om 10:10 heeft Tanya M. Lattner het volgende geschreven:
> 
> >> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build
> >> with the header files using uintptr_t (not recognised as a type).
> >> Putting "#include <stdint.h>" in
include/llvm/BasicBlock.h (llvm)
> >> and in "include/llvm/ValueSymbolTable.h" (frontend)
resolved this.
> >
> > Ok. This is now fixed on the release branch. Thanks!
> 
> The strange thing is that the configure process defines:
> 
> #define HAVE_STDINT_H 1
> 
> However, without literally including stdint.h (which should be  
> avoided as Reid mentioned) the compilation of AsmWriter.cpp goes  
> wrong, 
What goes wrong?
> although stdint.h, llvm/Support/DataTypes.h and inttypes.h are  
> all mentioned in AsmWriter.d:
.. snip ..
> Should -DHAVE_STDINT_H be passed to the above command?
No, it is defined in include/llvm/Config/config.h which is an autoconf
generated file and included in all LLVM compilations. 
> 
> >
> >> Also, I got linking errors while linking tblgen (see error.txt).  
> >> Any ideas about this?
> >
> > I'm not really sure whats going on here and I can't reproduce
this
> > since I don't have your setup. Its probably either an issue with  
> > gcc or ld (try upgrading to 2.17.X if possible). If you can try to  
> > investigate it further, that would be great. Then file a bug for it.
> 
> Problem solved: compiling the 2.0 frontend from source had resulted  
> in gcc, g++, ... instead of llvm-gcc, llvm-g++, ... After manually  
> renaming them, compilation of LLVM was a breeze and the tests did not  
> yield any unexpected failures (see attachment).
Glad you figured that out. The build guidelines for llvm-gcc are in
README.LLVM at the top level of the llvm-gcc source tree. It recommends
making links. Some of us, however, also use the --program-prefix=llvm-
option when configuring llvm-gcc which causes all programs to have an
llvm- prefix.
> 
> Kind regards,
> 
> Bram Adams
> GH-SEL, INTEC, Ghent University (Belgium)
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Bram Adams

2007-May-18 19:40 UTC

head link

[LLVMdev] Antw.: 2.0 Pre-release tarballs online

Hi,

Op 18-mei-07, om 18:40 heeft Reid Spencer het volgende geschreven:
> What goes wrong?
Everything's fine now. Forgot to look at Tanya's changes (#include  
"llvm/Support/DataTypes.h") :-)...
> Glad you figured that out. The build guidelines for llvm-gcc are in
> README.LLVM at the top level of the llvm-gcc source tree. It  
> recommends
> making links. Some of us, however, also use the --program-prefix=llvm-
> option when configuring llvm-gcc which causes all programs to have an
> llvm- prefix.
OK, I'lll use the latter option from now on.

Kind regards,

Bram Adams
GH-SEL, INTEC, Ghent University (Belgium)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20070518/f02d6594/attachment.html>

Possibly Parallel Threads

Search for more possibly parallel threads

llvm dev - May 2007 - [LLVMdev] Antw.: 2.0 Pre-release tarballs online

[LLVMdev] Antw.: 2.0 Pre-release tarballs online

[LLVMdev] Antw.: 2.0 Pre-release tarballs online

[LLVMdev] Antw.: 2.0 Pre-release tarballs online

Possibly Parallel Threads