From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Kuo Subject: Re: Removing architectures without upstream gcc support Date: Fri, 2 Mar 2018 19:43:06 -0600 Message-ID: <20180303014306.GA6911@codeaurora.org> References: <20180222191758.GB5180@codeaurora.org> <20180228020631.GB3780@codeaurora.org> Mime-Version: 1.0 Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1520041383; bh=Gqh5HMh3c8gaTAlS4HIxH+tEHxLHUp+dbYzkvmuObUQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ozUOulbOBYwzq/bQH3PjtFuygFZD4EL4+vnfEdOoGGkX/hzFiMACstgKrCSe7a4pL EwxGIbLwj5f+KiQdwcXkZLNZASxXxGc6iU0NfoTYfXz8VF8xlHUYqJvS4uY0XukAlk WGLW0+6EkEsri/x2aW1iWAAxtZH5Mq2yxWxi0iJo= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1520041382; bh=Gqh5HMh3c8gaTAlS4HIxH+tEHxLHUp+dbYzkvmuObUQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=lbKm5892sP01eNvYapHEjN0YbZnhxIV9vcGrMLYYALNzfTIxFTQqVSUkiq1zBJCSM GQBm30g99sT4HtAu8P/85kgFLDkRttzTh4utDycdMl1rYvm6cz1nTUPfvFvzjGbhZR CPyxc4Vsr413bprpIPVkaEylcmViX0yf+Xkox7w0= Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Arnd Bergmann Cc: linux-arch , Linux Kernel Mailing List , "open list:QUALCOMM HEXAGON..." , Chen Liqin , Lennox Wu , Guan Xuetao , Guenter Roeck , Al Viro , James Hogan , "open list:METAG ARCHITECTURE" , Jonas Bonn , Stefan Kristiansson , Stafford Horne , openrisc@lists.librecores.org, David Howells On Wed, Feb 28, 2018 at 09:37:09AM +0100, Arnd Bergmann wrote: > On Wed, Feb 28, 2018 at 3:06 AM, Richard Kuo wrote: > > On Thu, Feb 22, 2018 at 11:43:10PM +0100, Arnd Bergmann wrote: > >> - How do I build an llvm based toolchain for Hexagon? Do I need patches > >> on top of the llvm-6 release branch? Where can I find the corresponding > >> binutils-2.30 sources? > > > > Just to follow up on this, the closest thing right now to compile the kernel > > for Hexagon is the toolchain included with the Hexagon SDK. However, the > > linker will fail because of something in the kernel build process that > > I think produces empty sections, which that linker can't handle. A newer > > linker can handle it, but that's not scheduled to be released until much later > > this year. > > > > That's actually the closest option currently. I tried the upstream source > > but it seems to lack some specific patches to support kernel compilation, > > so I will need to chase those down. > > Thanks for trying it out. Can you point me to the sources? I tried downloading > a Hexagon SDK when I first looked at it, but only got a huge chunk of binary > java files and gave up before finding the llvm patches. I don't think the SDK patches are available externally. The good news is I think we're now one patch away from the upstream LLVM compiling a functional kernel for Hexagon (a few fixes to LLVM/clang have been committed already). It technically compiles but produces an abort (from a null deref) which the linker doesn't like. The linker itself unfortunately is going to be a different matter. Thanks, Richard Kuo -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project