All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Arnd Bergmann <arnd@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Cc: "open list:QUALCOMM HEXAGON..." <linux-hexagon@vger.kernel.org>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Brian Cain <bcain@codeaurora.org>,
	linux-arch <linux-arch@vger.kernel.org>,
	Guenter Roeck <linux@roeck-us.net>
Subject: Re: ARCH=hexagon unsupported?
Date: Fri, 23 Apr 2021 10:43:11 -0700	[thread overview]
Message-ID: <fa0bed95-5ddf-ecad-0613-2f13837578c3@infradead.org> (raw)
In-Reply-To: <CAK8P3a2DCCjOq+sB+9sRM7XrtnkromCs_+znv3dehqLiYFDQag@mail.gmail.com>

On 4/23/21 2:36 AM, Arnd Bergmann wrote:
> On Fri, Apr 23, 2021 at 12:12 AM 'Nick Desaulniers' via Clang Built
> Linux <clang-built-linux@googlegroups.com> wrote:
>>
>> Arnd,
>> No one can build ARCH=hexagon and
>> https://github.com/ClangBuiltLinux/linux/issues/759 has been open for
>> 2 years.
>>
>> Trying to build
>> $ ARCH=hexagon CROSS_COMPILE=hexagon-linux-gnu make LLVM=1 LLVM_IAS=1 -j71
>>
>> shows numerous issues, the latest of which
>> commit 8320514c91bea ("hexagon: switch to ->regset_get()")
>> has a very obvious typo which misspells the `struct` keyword and has
>> been in the tree for almost 1 year.
> 
> Thank you for looking into it.
> 
>> Why is arch/hexagon/ in the tree if no one can build it?
> 
> Removing it sounds reasonable to me, it's been broken for too long, and
> we did the same thing for unicore32 that was in the same situation
> where the gcc port was too old to build the kernel and the clang
> port never quite work in mainline.
> 
> Guenter also brought up the issue a year ago, and nothing happened.
> I see Brian still occasionally sends an Ack to a patch that gets merged
> through another tree, but he has not send any patches or pull requests
> himself after taking over maintainership from Richard Kuo in 2019,
> and the four hexagon pull requests after 2014 only contained build fixes
> from developers that don't have access to the hardware (Randy Dunlap,
> Viresh Kumar, Mike Frysinger and me).
> 
>        Arnd
> 
> [1] https://lore.kernel.org/lkml/04ca01d633a8$9abb8070$d0328150$@codeaurora.org/

There is no current gcc C compiler in the 3 locations that I know of to look.
The one I tried is v4.6 and it is too old to work with current makefiles.

-- 
~Randy


  reply	other threads:[~2021-04-23 17:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 22:12 ARCH=hexagon unsupported? Nick Desaulniers
2021-04-23  9:36 ` Arnd Bergmann
2021-04-23 17:43   ` Randy Dunlap [this message]
2021-04-23 18:17     ` Arnd Bergmann
2021-04-23 18:26       ` Miguel Ojeda
2021-04-23 19:31       ` Brian Cain
2021-04-23 20:26         ` Brian Cain
2021-04-23 20:26           ` Brian Cain
2021-04-23 21:47           ` Randy Dunlap
2021-04-23 22:25             ` Brian Cain
2021-04-23 22:26               ` Randy Dunlap
2021-05-19 15:28                 ` Brian Cain
2021-04-23 18:35   ` Brian Cain
2021-04-23 21:40     ` Nick Desaulniers
2021-04-26 13:13       ` Brian Cain

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=fa0bed95-5ddf-ecad-0613-2f13837578c3@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=arnd@kernel.org \
    --cc=bcain@codeaurora.org \
    --cc=clang-built-linux@googlegroups.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-hexagon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=ndesaulniers@google.com \
    /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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.