public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65837] [arm-linux-gnueabihf] lto1 target specific builtin not available Date: Tue, 28 Apr 2015 10:48:00 -0000 [thread overview] Message-ID: <bug-65837-4-g9YgAJIe0B@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65837-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65837 prathamesh3492 at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkuvyrkov at gcc dot gnu.org --- Comment #14 from prathamesh3492 at gcc dot gnu.org --- Hi, Following Maxim's suggestion I tried to build with x86_64-gcc passing -mtune=k8 at compile-time but not at link time and the same thing happens. gcc -flto -mtune=k8 foo.c -v: Without passing -mtune=k8 at link-time, -mtune=generic overrides -mtune=k8 gcc -flto foo.o -v: COLLECT_GCC_OPTIONS='-c' '-fmath-errno' '-fsigned-zeros' '-ftrapping-math' '-fno-trapv' '-fno-strict-overflow' '-fno-openmp' '-fno-openacc' '-mtune=k8' '-march=x86-64' '-v' '-mtune=generic' '-march=x86-64' '-fltrans-output-list=/tmp/cc415lAT.ltrans.out' '-fwpa' '-fresolution=/tmp/ccuL4EuS.res' /home/prathamesh.kulkarni/fsf-toolchain/libexec/gcc/x86_64-unknown-linux-gnu/6.0.0/lto1 -quiet -dumpbase foo.o -mtune=k8 -march=x86-64 -mtune=generic -march=x86-64 -auxbase foo -version -fmath-errno -fsigned-zeros -ftrapping-math -fno-trapv -fno-strict-overflow -fno-openmp -fno-openacc -fltrans-output-list=/tmp/cc415lAT.ltrans.out -fwpa -fresolution=/tmp/ccuL4EuS.res @/tmp/ccXLZx2S Passing -mtune=k8 at link-time, passes only -mtune=k8 to lto1 gcc -flto -mtune=k8 foo.o -v: COLLECT_GCC_OPTIONS='-c' '-fmath-errno' '-fsigned-zeros' '-ftrapping-math' '-fno-trapv' '-fno-strict-overflow' '-fno-openmp' '-fno-openacc' '-mtune=k8' '-march=x86-64' '-mtune=k8' '-v' '-march=x86-64' '-fltrans-output-list=/tmp/ccK0THy1.ltrans.out' '-fwpa' '-fresolution=/tmp/ccqMHR7Y.res' /home/prathamesh.kulkarni/fsf-toolchain/libexec/gcc/x86_64-unknown-linux-gnu/6.0.0/lto1 -quiet -dumpbase foo.o -mtune=k8 -march=x86-64 -mtune=k8 -march=x86-64 -auxbase foo -version -fmath-errno -fsigned-zeros -ftrapping-math -fno-trapv -fno-strict-overflow -fno-openmp -fno-openacc -fltrans-output-list=/tmp/ccK0THy1.ltrans.out -fwpa -fresolution=/tmp/ccqMHR7Y.res @/tmp/ccxcdoB1 So this looks like a target independent bug ? I am continuing to investigate it. Thank you, Prathamesh
next prev parent reply other threads:[~2015-04-28 10:48 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-04-21 20:28 [Bug target/65837] New: " prathamesh3492 at gcc dot gnu.org 2015-04-22 8:54 ` [Bug target/65837] " rguenth at gcc dot gnu.org 2015-04-22 19:53 ` prathamesh3492 at gcc dot gnu.org 2015-04-22 23:38 ` prathamesh3492 at gcc dot gnu.org 2015-04-23 8:18 ` rguenther at suse dot de 2015-04-23 8:18 ` rguenth at gcc dot gnu.org 2015-04-23 11:46 ` rguenth at gcc dot gnu.org 2015-04-23 12:18 ` prathamesh3492 at gcc dot gnu.org 2015-04-23 12:20 ` rguenther at suse dot de 2015-04-23 13:17 ` ramana at gcc dot gnu.org 2015-04-23 13:50 ` prathamesh3492 at gcc dot gnu.org 2015-04-23 13:52 ` ramana at gcc dot gnu.org 2015-04-28 10:48 ` prathamesh3492 at gcc dot gnu.org [this message] 2015-04-28 14:14 ` prathamesh3492 at gcc dot gnu.org 2015-04-28 19:22 ` prathamesh3492 at gcc dot gnu.org 2015-04-28 22:40 ` prathamesh3492 at gcc dot gnu.org 2015-04-29 7:42 ` rguenth at gcc dot gnu.org 2015-04-29 7:42 ` rguenther at suse dot de 2015-04-29 8:00 ` ramana at gcc dot gnu.org 2015-04-29 11:30 ` ramana.radhakrishnan at arm dot com 2015-05-05 15:18 ` ktkachov at gcc dot gnu.org 2015-05-19 13:44 ` chrbr at gcc dot gnu.org 2015-05-19 15:49 ` ramana at gcc dot gnu.org 2015-05-20 13:21 ` chrbr at gcc dot gnu.org 2015-06-22 8:22 ` chrbr at gcc dot gnu.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=bug-65837-4-g9YgAJIe0B@http.gcc.gnu.org/bugzilla/ \ --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).