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: Wed, 22 Apr 2015 23:38:00 -0000 [thread overview] Message-ID: <bug-65837-4-KrABaHIE73@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 ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from prathamesh3492 at gcc dot gnu.org --- (In reply to Ramana Radhakrishnan from comment #4) > (In reply to prathamesh3492 from comment #3) > > Hi, > > I tried to reproduce the error with a reduced test-case: > > > > #include "arm_neon.h" > > > > float32x2_t a, b, c, e; > > > > int main() > > { > > e = __builtin_neon_vmls_lanev2sf (a, b, c, 0); > > return 0; > > } > > > > arm-linux-gnueabihf-gcc -mfpu=neon test.c -flto test.c -c > > arm-linux-gnueabihf-gcc test.o -flto -o test > > lto1: fatal error: target specific builtin not available > > compilation terminated. > > Ofcourse, that's expected behaviour - you don't have support for the SIMD > intrinsics if you don't ask for it on the command line or your compiler > doesn't default to generating code for the SIMD unit. > > > lto-wrapper: fatal error: > > /home/prathamesh.kulkarni/gnu-toolchain/gcc-chromium-arm-linux-gnueabihf/ > > builds/destdir/x86_64-unknown-linux-gnu/bin/arm-linux-gnueabihf-gcc returned > > 1 exit status > > compilation terminated. > > > > However passing -mfpu=neon for linking works: > > arm-linux-gnueabihf-gcc -mfpu=neon test.o -flto -o test > > > > I suppose similar thing must be happening during linking > > libshared_memory_support.so for chromium build ? > > I couldn't see -mfpu=neon in the command line used for linking > > libshared_memory_support.so > > RESOLVED INVALID then ? Yeah, silly mistake from my side, sorry for the noise. Regards, Prathamesh > > regards > Ramana > > > > > Thank you > > Prathamesh
next prev parent reply other threads:[~2015-04-22 23:38 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 [this message] 2015-04-23 8:18 ` rguenth at gcc dot gnu.org 2015-04-23 8:18 ` rguenther at suse dot de 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 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 ` rguenther at suse dot de 2015-04-29 7:42 ` rguenth at gcc dot gnu.org 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-KrABaHIE73@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).