Re:Partial WebAssembly backend for the GNU toolchain
by astrange on Saturday March 04, 2017 @05:44PM
(#13793316)
gcc already has frontends (GIMPLE), backends (LTO and HSAIL) and plugins (DragonEgg) that do this, so you've had nothing to worry about for like five years now.
Re:Partial WebAssembly backend for the GNU toolchain
by hamandcheese on Saturday March 04, 2017 @05:26PM
(#13793236)
I don't really follow. Do you mean, for example, BigCorp making a backend that compiles to proprietary BigCorpLang? Why would that be such a bad thing?
Re:Partial WebAssembly backend for the GNU toolchain
by icebraining on Saturday March 04, 2017 @05:51PM
(#13793340)
Re:Partial WebAssembly backend for the GNU toolchain
by foota on Saturday March 04, 2017 @05:47PM
(#13793331)
I think they mean it compiles to BigBorp ir which is then used with BigCorps secret sauce optimizing compiler.
Re:Partial WebAssembly backend for the GNU toolchain
by bonzini on Sunday March 05, 2017 @08:51AM
(#13795985)
That's already happening with the nVidia PTX backend, so I guess that's accepted too nowadays.
Re:Partial WebAssembly backend for the GNU toolchain
by pekk on Saturday March 04, 2017 @06:57PM
(#13793670)
This isn't really a generic issue of "previous attempts" but more specifically LLVM, right?
Re:Partial WebAssembly backend for the GNU toolchain
by DannyBee on Saturday March 04, 2017 @07:25PM
(#13793828)
No, actually.
There's been a bunch, from java backends, etc.
Re:Partial WebAssembly backend for the GNU toolchain
by jacobush on Saturday March 04, 2017 @08:39PM
(#13794124)
Yes, Stallman killed the JVM backend. Did not want to promote a proprietary technology.
Re:Partial WebAssembly backend for the GNU toolchain
by comex on Saturday March 04, 2017 @08:50PM
(#13794164)
In retrospect (Oracle v. Google) that doesn't seem like such a bad decision!
Admittedly, the concern about the JVM backend was different from what got Google in trouble; indeed, GNU had their own reimplementation of Java (GCJ / GNU Classpath) which was equally potentially infringing (and was the main reason bytecode output was a problem in the first place - because GCC supported bytecode input already, it could allow for round tripping). But the overall message of avoiding proprietary programming languages/environments seems prescient.
Re:Partial WebAssembly backend for the GNU toolchain
by arthur2e5 on Saturday March 04, 2017 @09:11PM
(#13794224)
There is actually another voice from Free Software advocates on the Oracle v. Google case, basically saying that Google could have been free from Oracle's trolling in the first place had they based their thing on the GPL-licensed OpenJDK.
A sample of such statements, from https://github.com/biergaizi, can be found at http://weibo.com/1219205751/Dov1ynGLk (login-walled).
Re:Partial WebAssembly backend for the GNU toolchain
by JoshTriplett on Saturday March 04, 2017 @09:17PM
(#13794237)
OpenJDK didn't exist when Android first started; Dalvik pre-dates the initial release of OpenJDK, let alone the viable versions of OpenJDK that came after further development in the community.
In the past, backends for anything usable as an intermediate language received pushback as possible "escape hatches" by which one could glue proprietary code (whether frontends, backends, or optimization passes) into the GNU toolchain. That pushback mostly went away when the GCC Runtime Library Exception came out, which makes such proprietary combinations much less viable.
So, hopefully this will get merged, or at least get on the path to merging after further development.