public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/65464] [4.8/4.9 Regression] disabling multilib support for powerpc64le-linux-gnu breaks kernel builds Date: Thu, 19 Mar 2015 03:54:00 -0000 [thread overview] Message-ID: <bug-65464-4-7ZD3nv25Ea@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-65464-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65464 Alan Modra <amodra at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |amodra at gmail dot com Resolution|--- |WONTFIX --- Comment #3 from Alan Modra <amodra at gmail dot com> --- 32-bit support for powerpc64le hasn't been removed, it is just not enabled by default since we don't support a 32-bit user runtime. As Andrew said, it is a kernel bug that a 32-bit vdso is built. You can get 32-bit compiler support by configuring with --enable-targets=powerpcle-linux --disable-multilib if you so desire.
next prev parent reply other threads:[~2015-03-19 3:54 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-18 23:15 [Bug target/65464] New: " doko at gcc dot gnu.org 2015-03-18 23:20 ` [Bug target/65464] " doko at gcc dot gnu.org 2015-03-18 23:38 ` pinskia at gcc dot gnu.org 2015-03-19 3:54 ` amodra at gmail dot com [this message] 2015-03-19 6:09 ` trippels at gcc dot gnu.org 2015-03-19 15:15 ` doko at ubuntu dot com 2015-03-19 15:17 ` trippels at gcc dot gnu.org 2015-03-19 22:36 ` amodra at gmail dot com 2015-03-19 23:53 ` doko at gcc dot gnu.org 2015-03-20 8:36 ` trippels at gcc dot gnu.org 2015-03-20 8:42 ` trippels 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-65464-4-7ZD3nv25Ea@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).