[patch] Make r600 non-experimental

Laurent Carlier lordheavym at gmail.com
Wed May 22 05:12:41 PDT 2013


Le mardi 21 mai 2013 14:01:20 Rafael Espíndola a écrit :
> The r600 backend has been in tree for some time now. It has tests that
> are being maintained and there is even a buildbot that builds it.
> 
> We should probably stop calling it experimental. This should make sure
> that we don't accidentally break the build.
> 
> Is the attached patch OK?
> 
> Cheers,
> Rafael

I have currently this regression during configure step:

configure: creating ./config.status
config.status: creating include/llvm/Config/Targets.def
config.status: creating include/llvm/Config/AsmPrinters.def
config.status: creating include/llvm/Config/AsmParsers.def
config.status: creating include/llvm/Config/Disassemblers.def
config.status: creating Makefile.config
config.status: creating llvm.spec
config.status: creating docs/doxygen.cfg
config.status: creating tools/clang/docs/doxygen.cfg
config.status: creating bindings/ocaml/llvm/META.llvm
config.status: creating include/llvm/Config/config.h
config.status: creating include/llvm/Config/llvm-config.h
config.status: creating include/llvm/Support/DataTypes.h
config.status: creating tools/clang/include/clang/Config/config.h
config.status: executing setup commands
config.status: executing Makefile commands
config.status: executing Makefile.common commands
config.status: executing examples/Makefile commands
config.status: executing lib/Makefile commands
config.status: executing runtime/Makefile commands
config.status: executing test/Makefile commands
config.status: executing test/Makefile.tests commands
config.status: executing unittests/Makefile commands
config.status: executing tools/Makefile commands
config.status: executing utils/Makefile commands
config.status: executing projects/Makefile commands
config.status: executing bindings/Makefile commands
config.status: executing bindings/ocaml/Makefile.ocaml commands
=== configuring in projects/sample (/build/llvm-amdgpu-
svn/src/llvm/projects/sample)
configure: running /bin/sh ./configure --prefix=/usr '--with-
python=/usr/bin/python2' '--libdir=/usr/lib/llvm-3.4svn' '--sysconfdir=/etc' 
'--enable-shared' '--enable-libffi' '--enable-
targets=host,x86,x86_64,cpp,r600' '--disable-expensive-checks' '--with-
binutils-include=/usr/include' '--enable-optimized' 'CC=gcc' 'CFLAGS=-
march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-
size=4' 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro' 'CPPFLAGS=-
D_FORTIFY_SOURCE=2 -I/usr/lib/libffi-3.0.13/include ' 'CXX=g++' 'CXXFLAGS=-
march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-
size=4' --cache-file=/dev/null --srcdir=.
checking llvm-config... no
checking LLVM package version... unknown
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking type of operating system we're going to host on... Linux
checking type of operating system we're going to target... Linux
checking target architecture... x86_64
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
configure: error: Unrecognized target r600
configure: error: ./configure failed for projects/sample

with:
CC=gcc CXX=g++ \
./configure \
--with-python=/usr/bin/python2 \
--prefix=/usr \
--libdir=/usr/lib/llvm-${_llvmver} \
--sysconfdir=/etc \
--enable-shared \
--enable-libffi \
--enable-targets=host,x86,x86_64,cpp,R600 \
--disable-expensive-checks \
--with-binutils-include=/usr/include \
--$_optimized_switch-optimized

-- 
Laurent Carlier
ArchLinux Trusted User
http://www.archlinux.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20130522/0ede5b0c/attachment.sig>


More information about the llvm-commits mailing list