devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: [PATCH v2] kbuild: support byacc as alternative YACC to bison
@ 2019-11-11 18:37 Dmitry Golovin
  0 siblings, 0 replies; 5+ messages in thread
From: Dmitry Golovin @ 2019-11-11 18:37 UTC (permalink / raw)
  To: Masahiro Yamada
  Cc: Ethan Sommer, Michal Marek, Rob Herring, Frank Rowand,
	Sedat Dilek, Nathan Chancellor, Nick Desaulniers,
	Linux Kbuild mailing list, Linux Kernel Mailing List, DTML

> Hmm, this is unfortunate since there is no common way to
> specify the header path directly.
> 
> I am not sure how much effort we should invent
> to support non-GNU implementation
> since we already rely on various GNU tools.
> 
> If we decide to support byacc,
> we must carry the restriction
> that bans GNU-extension.

In fact Linux now can be built without using GNU
binutils and using LLVM tools instead. It's just
one architecture and a specific config now, but
eventually the others will be built too. You can
follow the progress here:
https://github.com/ClangBuiltLinux/continuous-integration/issues/73

I believe that compatibility with different
alternative tools is a good thing as long as it
doesn't add unwanted complexity. And as this patch
is just changing command-line flags to their
portable variants and explicitly adds a couple of
definitions that are presumed by GNU bison, I
can't see a problem with it.

Regards,
Dmitry

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2019-11-11 18:43 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <CAK7LNASG4GzaU6SR=ThfJpjrqmC53xmcSMAWqppciWbx3jMgdw@mail.gmail.com>
2019-10-29 15:01 ` [PATCH v2] kbuild: support byacc as alternative YACC to bison Ethan Sommer
2019-10-29 15:58   ` Frank Rowand
2019-10-30  2:58   ` Masahiro Yamada
2019-11-03 20:30     ` Ethan Sommer
2019-11-11 18:37 Dmitry Golovin

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 NNTP newsgroup(s).