Skip to content

Failed to build x64 vm in release mode #4609

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DartBot opened this issue Aug 20, 2012 · 4 comments
Closed

Failed to build x64 vm in release mode #4609

DartBot opened this issue Aug 20, 2012 · 4 comments
Assignees
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant

Comments

@DartBot
Copy link

DartBot commented Aug 20, 2012

This issue was originally filed by [email protected]


What steps will reproduce the problem?

  1. ../tools/build.py -m release --arch=x64 -j 8

What is the expected output? What do you see instead?
Several of:
out/ReleaseX64/obj.target/runtime/../libdart_vm/runtime/vm/raw_object_snapshot.o: In function dart::ExternalInt8Array::ReadFrom(dart::SnapshotReader\*, long, long, dart::Snapshot::Kind)': /home/nfgs/Programacao/Dart/vm/runtime/../runtime/vm/raw_object_snapshot.cc:1889: undefined reference todart::RawExternalInt8Array* dart::ByteArray::NewExternalImpl<dart::ExternalInt8Array, dart::RawExternalInt8Array, signed char>(dart::Class const&, signed char*, long, void*, void ()(void), dart::Heap::Space)'

What version of the product are you using? On what operating system?
Latest from bleeding_edge (10977) on Ubuntu with gcc 4.5.2

../tools/build.py -m debug --arch=x64 -j 8 builds just fine.

@larsbak
Copy link

larsbak commented Aug 21, 2012

Seems like inlining of C++ templates changed from gcc 4.4.3 to gcc 4.5.2.


Set owner to @iposva-google.
Added Area-VM label.

@larsbak
Copy link

larsbak commented Aug 21, 2012

Added Triaged label.

@DartBot
Copy link
Author

DartBot commented Sep 11, 2012

This comment was originally written by [email protected]


uname -a

Linux dev.gc.kiev.ua 3.0.39-std-def-alt0.M60P.1 #­1 SMP Sat Aug 4 06:41:48 UTC 2012 x86_64 GNU/Linux

$ gcc -v
Using built-in specs.
COLLECT_GCC=x86_64-alt-linux-gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-alt-linux/4.5.3/lto-wrapper
Target: x86_64-alt-linux
Configured with: ../configure --host=x86_64-alt-linux --build=x86_64-alt-linux --target=x86_64-alt-linux --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var/lib --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --disable-dependency-tracking --without-included-gettext --program-suffix=-4.5 --with-slibdir=/lib64 --with-bugurl=http://bugzilla.altlinux.org --enable-bootstrap --enable-shared --enable-__cxa_atexit --enable-threads=posix --enable-checking=release --with-system-zlib --without-included-gettext --enable-multilib --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,fortran,objc,obj-c++,java,ada,lto --enable-plugin --enable-java-awt=gtk --with-native-libdir=/usr/lib64/gcj-4.5 --with-ecj-jar=/usr/share/java/ecj.jar --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.5-1.5.0.0/jre --enable-libgcj-multifile --disable-libjava-multilib --enable-java-maintainer-mode --with-arch_32=i586 --with-tune_32=generic
Thread model: posix
gcc version 4.5.3 20120403 (ALT Linux 4.5.3-alt1.M60P.1) (GCC)


Attachment:
build.log (10 KB)

@iposva-google
Copy link
Contributor

I have not recently heard complaints about newer versions of gcc failing.


Added AssumedStale label.

@DartBot DartBot added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant labels May 29, 2013
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-vm Use area-vm for VM related issues, including code coverage, and the AOT and JIT backends. closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Development

No branches or pull requests

3 participants