public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fpbeekhof at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/39573] Linking fails on AMD with -march=native, works with generic x86_64 Date: Sat, 04 Apr 2009 19:50:00 -0000 [thread overview] Message-ID: <20090404195010.28538.qmail@sourceware.org> (raw) In-Reply-To: <bug-39573-14973@http.gcc.gnu.org/bugzilla/> ------- Comment #11 from fpbeekhof at gmail dot com 2009-04-04 19:50 ------- No problem. I did a few more tests... In short, it's the combination of -fopenmp and -march=native that makes fail on AMD64. Note: To test without openMP you can't use the preprocessed source. # openmp and march=native --> FAIL $ make clean; make CNF=gcc BACKEND=gsl .... g++ -o tinystr.o -c -pipe -I. -Wall -fopenmp -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinystr.cpp g++ -o main.o -c -pipe -I. -Wall -fopenmp -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ main.cpp g++ -o tinyxml.o -c -pipe -I. -Wall -fopenmp -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxml.cpp g++ -o tinyxmlerror.o -c -pipe -I. -Wall -fopenmp -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxmlerror.cpp g++ -o tinyxmlparser.o -c -pipe -I. -Wall -fopenmp -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxmlparser.cpp g++ -o shapes -fopenmp -DUSE_GSL -L/user/l1/beekhof//lib/ tinystr.o tinyxml.o tinyxmlerror.o tinyxmlparser.o main.o -lcvmlcpp -lz -lboost_iostreams -lgsl -lgslcblas main.o: In function `_ZN7cvmlcpp25extractSurfaceFromAdapterIN6shapes20ShapeSurfaceAdaptor_IdEEdEEvRKT_RNS_8GeometryIT0_EEd.omp_fn.9': main.cpp:(.text+0x11cc): undefined reference to `_ZN7cvmlcpp25extractSurfaceFromAdapterIN6shapes20ShapeSurfaceAdaptor_IdEEdEEvRKT_RNS_8GeometryIT0_EEd.omp_fn.9::C.467' collect2: ld returned 1 exit status scons: *** [shapes] Error 1 scons: building terminated because of errors. make: *** [compile] Error 2 # No march=native --> FINE $ make clean; make CNF=gcc BACKEND=gsl .... g++ -o tinystr.o -c -pipe -I. -Wall -fopenmp -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinystr.cpp g++ -o main.o -c -pipe -I. -Wall -fopenmp -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ main.cpp g++ -o tinyxml.o -c -pipe -I. -Wall -fopenmp -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxml.cpp g++ -o tinyxmlerror.o -c -pipe -I. -Wall -fopenmp -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxmlerror.cpp g++ -o tinyxmlparser.o -c -pipe -I. -Wall -fopenmp -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxmlparser.cpp g++ -o shapes -fopenmp -DUSE_GSL -L/user/l1/beekhof//lib/ tinystr.o tinyxml.o tinyxmlerror.o tinyxmlparser.o main.o -lcvmlcpp -lz -lboost_iostreams -lgsl -lgslcblas scons: done building targets. # No openmp --> FINE $ make clean; make CNF=gcc BACKEND=gsl .... g++ -o main.o -c -pipe -I. -Wall -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ main.cpp g++ -o tinystr.o -c -pipe -I. -Wall -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinystr.cpp g++ -o tinyxml.o -c -pipe -I. -Wall -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxml.cpp g++ -o tinyxmlerror.o -c -pipe -I. -Wall -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxmlerror.cpp g++ -o tinyxmlparser.o -c -pipe -I. -Wall -march=native -DNDEBUG -DUSE_GSL -I/user/l1/beekhof//include/ tinyxmlparser.cpp g++ -o shapes -DUSE_GSL -L/user/l1/beekhof//lib/ tinystr.o tinyxml.o tinyxmlerror.o tinyxmlparser.o main.o -lcvmlcpp -lz -lboost_iostreams -lgsl -lgslcblas scons: done building targets. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39573
next prev parent reply other threads:[~2009-04-04 19:50 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-03-28 15:42 [Bug other/39573] New: linking fails when optimizations are enabled fpbeekhof at gmail dot com 2009-04-03 12:01 ` [Bug other/39573] " fpbeekhof at gmail dot com 2009-04-04 16:57 ` fpbeekhof at gmail dot com 2009-04-04 17:30 ` [Bug target/39573] Linking fails on AMD with -march=native, works with generic x86_64 steven at gcc dot gnu dot org 2009-04-04 17:40 ` rguenth at gcc dot gnu dot org 2009-04-04 17:45 ` fpbeekhof at gmail dot com 2009-04-04 17:47 ` rguenth at gcc dot gnu dot org 2009-04-04 18:02 ` fpbeekhof at gmail dot com 2009-04-04 18:04 ` rguenth at gcc dot gnu dot org 2009-04-04 18:13 ` fpbeekhof at gmail dot com 2009-04-04 18:41 ` steven at gcc dot gnu dot org 2009-04-04 19:50 ` fpbeekhof at gmail dot com [this message] 2009-04-04 20:00 ` rguenth at gcc dot gnu dot org 2009-04-04 20:03 ` rguenth at gcc dot gnu dot org 2009-04-04 20:15 ` [Bug target/39573] Linking fails on AMD with -march=native and -fopenmp, " fpbeekhof at gmail dot com 2009-04-04 20:45 ` rguenth at gcc dot gnu dot org 2009-04-05 8:17 ` fpbeekhof at gmail dot com 2009-04-06 8:59 ` jakub at gcc dot gnu dot org 2009-04-08 20:05 ` [Bug middle-end/39573] " jakub at gcc dot gnu dot org 2009-04-08 20:14 ` jakub at gcc dot gnu dot org 2009-04-08 20:14 ` jakub at gcc dot gnu dot org 2009-04-28 23:41 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20090404195010.28538.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).