public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "alex.buell at munted dot org.uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/47962] New: media-libs/xvid-1.3.0 fails to build on SPARC unless -mvis flag stripped Date: Wed, 02 Mar 2011 21:19:00 -0000 [thread overview] Message-ID: <bug-47962-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47962 Summary: media-libs/xvid-1.3.0 fails to build on SPARC unless -mvis flag stripped Product: gcc Version: 4.4.4 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: alex.buell@munted.org.uk Host: SPARC64 Target: SPARC64 Build: SPARC64 Using -mcpu=ultrasparc3 -mvis results in xvi-1.3.0 failing to compile its source. Symptoms include the following: standard input}:11751: (Requires v9|v9a|v9b; requested architecture is sparclite.) {standard input}:11781: Error: Architecture mismatch on "bge,pn %icc,.LL483". {standard input}:11781: (Requires v9|v9a|v9b; requested architecture is sparclite.) {standard input}:11787: Error: Architecture mismatch on "bl,a,pt %icc,.LL522". {standard input}:11787: (Requires v9|v9a|v9b; requested architecture is sparclite.) {standard input}:11792: Error: Architecture mismatch on "be,a,pn %icc,.LL523". {standard input}:11792: (Requires v9|v9a|v9b; requested architecture is sparclite.) {standard input}:11819: Error: Architecture mismatch on "return". {standard input}:11819: (Requires v9|v9a|v9b; requested architecture is sparclite.) {standard input}:11832: Error: Architecture mismatch on "fcmped". my solution was to remove the -mvis flag, and all was well.
next reply other threads:[~2011-03-02 21:19 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-02 21:19 alex.buell at munted dot org.uk [this message] 2011-03-03 10:12 ` [Bug c/47962] " rguenth 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-47962-4@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).