11 ms·
Defending GCC considered futile
- nothrabannosir 12y agoObsolescence happens; this is nobody's fault. It will happen to clang/LLVM someday, too, but today is not that day. This is a beautiful line. Very wise, and it will hopefully help soothe the otherwise pretty harsh message.
- lultimouomo 12y agoESR seems a bit over the line with this mail, but what never ceases to amaze me is how RMS is disconnected with the present technology: >From its name, I guess that LLDB is a noncopylefted debugger and that some might intend it to replace GDB. But I don't know if that is so. This is just one of many, in the recent arguments he has stated several times that he doesn't understand how automated code refactoring works, he has not experience with IDEs, and things of the like. Beside the ideological point, he does not seem a person capable of steering important projects, at least when it comes to compiler technology. He just doesn't know enough anymore.
- zak_mc_kracken 12y agoIt's not just that his knowledge is outdated, it's also that his philosophical principles will always take precedence over everything else, which includes sound and/or pragmatic technological decisions. I'm not fond of esr in general but he's spot on with this post.
- nailer 12y ago> it's also that his philosophical principles will always take precedence over everything else Exactly. I respect RMS, and his position that proprietary software is immoral, but I also know that position won't be shared by many (maybe even most) of the people who care about free software.
- josteink 12y ago> It's not just that his knowledge is outdated, it's also that his philosophical principles will always take precedence over everything else To be fair to RMS he has tried to consider opposing views in the past when he can see and understand the need behind the proposition. In this case the problem is that RMS doesn't know enough C++/Java/C#-style OO programming, and can't understand why you would need refactoring tools to rename a method, because in his C-style world a search and replace should be sufficient. And because he doesn't see the need himself, he wont consider it a valid use-case which GNU/GCC/Emacs needs to support. This already has lead to chilling effects: People have stopped working on adding GCC-based support for auto-completion and similar functionality. RMS may be stubborn, but he's not stupid: He sees adding the proposed LLDB/LLVM-based functionality as a direct consequence of this, and bypassing his "authoriity" on the GCC-issue and thus an "attack" on GCC and the goals of GNU/FCC itself. In my mind, he is obviously right that people are side-stepping his judgement, but he is wrong that this is an attack on free software: People just want to make Emacs better, and he is vigorously fighting them to make it not happen. And now we have RMS fighting to artificially limit free software, in his mind to preserve it. I'm not sure how long this has been going on now... A decade? To me forking core GNU projects to leave RMS out just in order to get things done is increasingly looking like the only option.
- hga 12y ago"People just want to make Emacs better, and he is vigorously denying people the features they ask for." And while I have as of yet no opinion on the concept, a lot of people believe he's hypocritical for supporting non-free OSes in GCC and Gnu Emacs.
- thoth 12y agoI believe the explanation here is that the FSF/GNU is willing to support their tools on non-free OSes as long as those tools work the same as the do on free OSes, and in particular, don't work "better" as compared to the free version because the non-free OS provides additional services somehow. They don't want their tools to be superior or have better functionality on a non-free OS. For example, emacs wouldn't take a patch that hooked into speech recognition provided by the OS, unless that was also available on a free OS. And say Microsoft or Apple provided powerful functionality for debuggers via a system api (and this same functionality isn't on a free OS) - gdb would not take a patch that used it.
- the_af 12y agoNote this is explicitly RMS' philosophy, which hasn't changed. For him, freedom takes precedence over technological quality. He has been saying this for ages, for example when he explained that Open Source (as represented by Eric Raymond) and Free Software (as represented by the FSF) have very different goals. If you accept that RMS' worldview is about freedom, even if it sometimes means sacrificing some technological advantages, you'll see his position is consistent and reasonable.
- amyjess 12y agoThe problem is that the number of users is directly proportional to technological quality. People use gcc over non-copyleft compilers because they perceive it as technically superior. People use emacs over non-copyleft editors because they perceive it as technically superior. Sacrificing technological quality to fulfill an agenda will actually have the opposite effect, because it'll drive users to non-copyleft solutions in order to get the better piece of software. It's not just the number of users, either. When your software is dominant, you're in control. You get to have a say in the direction of the technology, and you get to prevent the lesser players from having their say. By sacrificing technological quality for ideological purity, RMS is giving up both his userbase and his dominant position he can use to prevent non-free software from taking over.
- zak_mc_kracken 12y agoHis position is certainly consistent but definitely not reasonable.
- maxlybbert 12y agoYes, this is a perfect example of the difference between open source and free software. I remember Stallman saying something along the lines of "even if it weren't as good as proprietary software, it would be important for people to use free software" over a decade ago. The fact that releasing the source code, and allowing people to modify it, leads to high quality software is a nice perk as far as he's concerned; but it's not the reason for the FSF. The FSF exists so that programmers aren't helpless when their system breaks. Raymond's arguments, on the other hand are all about which compiler or debugger is better, assuming the compilers and debuggers being compared are open source.
- rayiner 12y agoWe're talking about a C compiler and debugger. Lots of very technically knowledgable people shun IDEs and automated refactoring in that space.
- Tomte 12y agoSure, that's a valid choice. But when you're implementing a language ecosystem, proud ignorance of other peoples' usage patterns is just embarassing.
- danieldk 12y agoIs RMS still involved with gcc at all? (Non-philosophically?)
- ekianjo 12y agoHe claims not doing any development himself for several years now, so I guess this means no.
- rayiner 12y agoDoes proud ignorance of IDEs indicate that RMS may be impolitic or undiplomatic? Yes. Does it indicate he "is disconnected with the present technology?" In the world of C/C++, I don't think being willfully ignorant of IDEs and automated refactoring means you are out of date in your technical knowledge, as the grandparent post implied.
- eropple 12y agoI do. There's a reason that CLion is becoming a thing (can't happen fast enough) and Visual Assist has been a de facto standard in C++ development on Windows for years. The tools exist, they just don't exist in Emacs.
- coldtea 12y agoNot that many. Except if Windows C++ developers (most of which use VS) don't qualify as "technically knowledgable people". And who is doing the judging?
- weenie 12y agoYou have to realize that RMS's goal isn't to "steer important projects", and you should give him more credit in that he probably could be "connected with the present technology" if he wanted to. The fact that "he doesn't know enough anymore" doesn't say much about Stallman; instead it says a lot about how his goal of making sure software is libre has been shoved aside by everyone else for other priorities. Also, RMS is one of the most humble people on the scene, and will freely admit to not knowing something until he lives and breathes it.
- hga 12y ago"You have to realize that RMS's goal isn't to 'steer important projects'" Not as such, but as long as he's doing it for so many marque GNU/FSF projects....
- weenie 12y agoOut of necessity and as a means to an end, because nobody else sharing his philosophy is willing to do it.
- dragonwriter 12y ago> Out of necessity and as a means to an end, because nobody else sharing his philosophy is willing to do it. I think that's a pretty striking description of failure in promoting an ideology.
- hga 12y agoOr at least his interpretation of that ideology. I'd be really surprised if most of the people working on these marque GNU/FSF projects weren't happy with GPL/copyleft, at least for these "complete" programs (as opposed to libraries like the GPLed GNU Scientific Library).
- 59nadir 12y ago> I think that's a pretty striking description of failure in promoting an ideology. Are you actually saying you think the FSF have failed?
- pnathan 12y agoear periodically shoves his oar into the FSF world, occasionally with faint malice about the whole business. He really isn't into Free software as much as he is into Open software. You can't read him as a disinterested techie and come away with correct views.
- lultimouomo 12y agoI think the many replies that point out that you don't need an IDE or code refactoring if you are a real programmer miss that my point is not that you need to use advanced tools to develop a compiler, is that you need to write a compiler that supports those tools for the people who like to use them. And to write such compiler, you must as a minimum know what refactoring tools and IDEs are. Also, I'm sure you always get naming and signatures right at the first try, foreseeing every possible evolution of the system. I don't, and since I don't like my programs to turn into huge piles of horror, I enjoy refactoring tools a lot.
- copsarebastards 12y agoSaying Stallman isn't qualified to steer major projects because he isn't familiar with IDEs is a pretty weird point to make. Emacs is a far more advanced environment than any IDE I have used, and often the so-called "features" of IDEs are to deal with self-created problems: Java/C# build tooling in IDEs, for example, is there to deal with the fact that the build processes for these languages is massively overcomplicated. I can't speak for Stallman, but I am confident that I'm accurately representing the opinions of a lot of Emacs users when I say that IDEs provide a leaky abstraction over systemic design problems rather than solving them.
- michaelhoffman 12y agoThankfully, Emacs maintainer Stefan Monnier is being sensible about this: > As mentioned earlier, in any case I will happily accept and install LLDB support into gud.el. So as long as I'm Emacs maintainer, your opinion on whether this might ruin the FSF's goals are not relevant. https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00498.html https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00...
- dekhn 12y agoYeah. What's especially painful is RMS is basically saying "Hey folks, I want to block this until I can research the issue." And then his research is "I don't know anuything about this, can anybody tell me what LLDB is?" My guess is (based on his past statements) that he doesn't browse the web, or browses it through emacs sending mail to him (really!) and doesn't use search so he can't really find out what LLDB is. Do you really want to be beholden to a person who blocks software integration (into a unified debugger interface) and then can't even do reearch to justify that?
- longlivegnu 12y agoYes, RMS does not "browse the web" he has a server that runs a script sort of like wget or cURL.
- protomyth 12y agoIs there a source for why he doesn't "browse the web"? I've read about how he does it, but the articles I have seen are very light on the reason.
- tjr 12y agohttps://stallman.org/stallman-computing.html https://stallman.org/stallman-computing.html I've never heard him flat-out say "why", but it sure appears to be in order to maximize anonymity / privacy on the web.
- 12y ago
- vezzy-fnord 12y agoThis is pretty much the perfect moment for two egos like RMS and ESR to clash. RMS is already getting a lot of flak for expressing his fear of GCC being displaced in such a manner, whereas ESR is well known for his disliking RMS, to put it mildly.
- neindanke 12y agoIt is not clear that RMS is driven by ego. He's motivated by a very clear goal to keep free software free. Free as in freedom free. As for ESR, well, yup, that's an ego that is sufficient in size to have a gravitational pull. http://www.linuxtoday.com/infrastructure/2000082800620OPCYKN http://www.linuxtoday.com/infrastructure/2000082800620OPCYKN
- hga 12y agoI think this is an unuseful definition of ego. I had a significant degree of contact with RMS in the period leading up to the launch of GNU, including being one of his roommates when he formally launched it, and I assure you he's very seriously ego driven. Are not his expounding etc. of his Free Software philosophy, a rather big thing as in a set of principles etc., the actions of a man very certain about himself? I think you're just perceiving a difference in how it's expressed by each of them, e.g. one reply is that ESR has a very clear goal of increasing the quality of software. Which for me is the big difference between "Free" and "Open" software.
- ekianjo 12y ago> seriously ego driven Oh, he is certainly ego-driven, but not in the same way as Jobs was, for example. RMS does not put his person before everyone else, but he lives rather through his principles and tries to convince everyone why it makes sense to follow them. And he has a very solid rationale he has developed through the years, making him very articulated.
- dragonwriter 12y ago> It is not clear that RMS is driven by ego. He's motivated by a very clear goal to keep free software free. No, he's driven by a very clear goal to prevent non-free software, even if that means preventing free software that might, potentially, in the future, be used by someone, somewhere, to create non-free software. And I think there is a certain amount of ego in there that gets in the way of good judgement on means, in that he tends to take actions which will naturally result in the free software he protects from being involved in producing non-free software losing mindshare to either non-free software or free software not wrapped around with his preferred restrictions, which is contradictory to his purpose -- since it means that not only does software that isn't crippled in features to prevent its utility in contributing non-free software wins, but that that software is also itself either non-free software, or non-copyleft free software that can more readily directly contribute to non-free software as well as being used by people who might build non-free software through use of the features of the software.
- hywel 12y ago> Already my own experiments suggest that LLVM is a superior compiler, by every metric I know of Except that it isn't copyleft, which is one of the most important metrics to Stallman, FSF et al, and is why they're unlikely to stop defending it.
- gcp 12y agoIf clang/LLVM caught up in generated code performance to GCC then I must admit that is news to me.
- ykl 12y agoSince clang 3.5 (or possibly even earlier), clang has basically been neck-in-neck with GCC. Most benchmarks seem to show the two basically equal to each other, and then there's a handful where clang wins outright and a handful where GCC wins outright. [1] For my own use-case (a high-performance photorealistic renderer threaded using TBB), my clang builds outperform my gcc builds, but of course that's completely anecdotal and based on just my own use-case. [1] http://www.phoronix.com/scan.php?page=article&item=gcc49_compiler_llvm35&num=1 http://www.phoronix.com/scan.php?page=article&item=gcc49_com...
- Htsthbjig 12y agoIt is copyleft. In fact they leave you more rights to copy the source than GPL.
- tjr 12y agohttp://www.gnu.org/copyleft/ http://www.gnu.org/copyleft/
- hywel 12y agoFrom http://llvm.org/docs/DeveloperPolicy.html#license http://llvm.org/docs/DeveloperPolicy.html#license: "LLVM’s license is not a “copyleft” license like the GPL." Rights to copy the source is not what copyleft means.
- tree_of_item 12y ago
- lwh 12y agoMaking your own tool suck/break/be-difficult when license-compatible patches are submitted to improve the program seems counter productive for everyone.
- jhildings 12y agoNice to see some classic maillist arguing instead of those hipster medium.com articles or posts full of memes/gif/clipart to make a point
- zanny 12y agoSo this was a discussion in /r/linux last week about LLVM and GCC et al, so I'm just reposting my statements on why a world where GCC is irrelevant is bad: It takes little effort on Apples or Googles or Microsofts part to take advantage of an LLVM dominated world to close off their own changes to it and try to force developers to use their own proprietary LLVM distributions on their own operating systems. It stops every other company in the future from taking advantage of all the great LLVM tech to implement their own CPUs in terms of LLVM IR, so they never need to publish their ISA and they can lock down their platform with a blob LLVM of their own. The only thing stopping any of that from happening is GCC being a still competitive alternative. If LLVM came to dominate the compiler scene to such a degree that GCC were irrelevant, it opens the flood gates to any major company forking LLVM into a proprietary paid for compiler that they require on their OS to profit from. It lets you do anything from what Apple is already doing with Swift, where you create a programming language with a proprietary compiler, or you could go from the other end and implement a proprietary translation unit so that you never need to publish your ISA (something Nvidia never does) but that allows all the LLVM compilers to target it. Right now, nobody can close off their LLVM contributions because a hobbled and fractured LLVM ecosystem is one that cannot overcome GCC. In the same way Apple and Google had to cooperate on webkit until it was so dominate they were in a position to fork and do their own things with it once Gecko was rendered effectively irrelevant, but the difference is that webkit was LGPL and Clang is its own permissive license - they still cannot directly modify the free software parts without redistribution, so it is harder to make a proprietary webkit, but Apple surely has succeeded since they have their own proprietary patchset on top of trunk webkit nowadays.
- gcp 12y agoOne of the big advantages of LLVM's license in this regard is that, unlike GCC, you don't risk leaking patents either even if you did open source it. Or did they fix that now?
- DannyBee 12y agoLLVM's developer policy has required free patent grants for many years, and a number of companies have done so. (a different number simply don't patent stuff they contribute to LLVM)
- danieldk 12y agoAlready my own experiments suggest that LLVM is a superior compiler, by every metric I know of, I know OpenMP/Clang, but as far as I know OpenMP is not upstreamed in clang yet, is it? If not, it's not superior yet in scientific computing :). But it will happen soon. And at the very least, LLVM's approach has created a large ecosystem that gcc did not have.
- dekhn 12y agoOpenMP only covers a subset of scientific computing.
- alayne 12y agoI don't know why you would make this argument now. Stallman argued clearly in January why copyleft was more important to him than technical superiority. https://gcc.gnu.org/ml/gcc/2014-01/msg00247.html https://gcc.gnu.org/ml/gcc/2014-01/msg00247.html
- ginko 12y agoWhich is kind of sad, since the major reason why GCC took off in the first place was because it was technically superior. http://utcc.utoronto.ca/~cks/space/blog/unix/GccEarlyEnthusiasm http://utcc.utoronto.ca/~cks/space/blog/unix/GccEarlyEnthusi...
- cwyers 12y agoEverybody already knew that copyleft was more important to Stallman than technical superiority. The problem is that there are a lot of people who put a higher value on technical superiority than copyleft. Those people could be counted upon as GCC users and contributors as long as GCC was the technically best compiler available as open source (all free software is open source, not all open source is free software, etc.). RMS's goal seems to be to have GCC not be replaced by LLVM. From a reply downthread of ESR's post: > This means it is more than a potential problem. > The possible harm is to replace copylefted GNU package with noncopylefted code. They must have worked for a long long time to replace the capabilities GDB already had. So RMS thinks it's a "problem" and "harmful" if lldb replaced gdb. So RMS cares not just about what GCC does, but whether or not other people adopt GCC as well. In terms of that goal, it does not matter what RMS considers more important. RMS is not going to convince everyone else to use GCC instead of LLVM by simply restating his arguements about copyleft forcefully again and again. That doesn't mean he has to sacrifice his feelings about copyleft. But it does mean he has to give a damn about being technically superior to LLVM and lldb if he wants to beat them.
- vidarh 12y agoHe does not need to beat LLVM for GCC to remain available. It would be detrimental to GCC to lose developers, sure, but I think one of the reasons for the disconnect between RMS and others is that RMS' goals does not require a large user base, and so he is willing to make decisions that seems counterproductive to anyone who cares about usability and user acceptance first. The mere continued existence of GCC (and the other GNU tools) in many ways safeguards the freedoms he cares about: It allows users to jump ship if they in the future are prevented from doing what they want with the alternatives. It's not the ideal scenario, but it better serves his goals than giving in, and potentially see these freedoms slipping away at some future point. Of course he'd be better served by GCC outcompeting LLVM. But if that isn't happening, his goals are better served by slowing developer migration than "capitulating" in a way that might affect developer mindshare by putting LLVM tools in front of more people. As you say, of course the problem with this is that a lot of us care more about the technical superiority. Especially when the competition is a project that is as open as LLVM.
- josteink 12y agoThis quarrel should be considered in context of the LLDB patch being submitted to gud.el. For those who want to read it from the start: http://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00274.html http://lists.gnu.org/archive/html/emacs-devel/2015-02/msg002... What made it a mega-thread was when RMS weighed in: http://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00360.html http://lists.gnu.org/archive/html/emacs-devel/2015-02/msg003...
- sanxiyn 12y agoThis is a bit over the top. As the rest of the thread points out, GCC in general still generates faster code than LLVM. "What does it take to get LLVM as performant as GCC" talk from 2014 LLVM Developers' Meeting discusses details. http://llvm.org/devmtg/2014-10/Slides/Molloy-LLVM-Performant-As-GCC-llvm-dev-2014.pdf http://llvm.org/devmtg/2014-10/Slides/Molloy-LLVM-Performant... "GCC versus LLVM performance analysis reveals the LLVM inliner 1) does not inline certain hot functions unless a high threshold is provided at -O3 2) produces larger and slower code at -Os." The problem of LLVM inliner has been known for a long time. One of the best discussion is "Optimization in LLVM" talk from 2013 European LLVM Conference. http://www.irill.org/videos/euro-llvm-2013/carruth-hires http://www.irill.org/videos/euro-llvm-2013/carruth-hires
- darkpore 12y agoDoes it? http://imagine-rt.blogspot.co.uk/2014/12/c-compiler-benchmarks.html http://imagine-rt.blogspot.co.uk/2014/12/c-compiler-benchmar...
- phkahler 12y agoWhy yes, yes it does. There are exceptions of course, you seem to have found one. Here are some others: http://www.phoronix.com/scan.php?page=article&item=gcc49_compiler_llvm35&num=1 http://www.phoronix.com/scan.php?page=article&item=gcc49_com...
- sanxiyn 12y agoYes it does. Did you read my links? Small benchmarks can go either way, but for large codebase (especially C++) inliner is more important than just about anything else. So GCC wins, because it has better inliner.
- darkpore 12y agoYep - you evidently didn't read mine as 165 k lines of c++ isn't exactly a small benchmark :) Anecdotal, but I've seen similar improvements over g++ in my code.
- Aqueous 12y agoDespite the inflexibility of RMS' arguments (they grate on me as much as anyone) I feel like his position on continuing to develop GCC without modern features like a fully exposed AST is necessary to keep the "moderate" position where it is. In other words, RMS' radical position is necessary for 'moderate' LLVM to exist. Otherwise we'd still be living in the Borland/Metrowerks/Microsoft world of the 90s - proprietary toolsets developed by private companies with absolutely no intention or incentive to share their code. In polisci there is a concept called the "Overton window." If a once-extremely radical position is held and promoted by any significant number of people, it shifts the entire conversation in that direction so that the formerly radical position seems more moderate. That's why RMS is very necessary. He shifts the Overton Window towards what most of us consider the "reasonable" position.
- dekhn 12y agoSimilarly in negotiating there is a term 'blue sky proposal' which is so extreme that people end up shifting their acceptable terms.
- danielweber 12y agoThere is also overplaying your hand and making the other person leave the room.
- cynicalkane 12y agoThis is false--people are just as likely to respond to opposing arguments with rejection and ideological hardening. This is replicated in psychological studies. In my personal experience, the less the opposing position acknowledges the values of its opponents, the more likely it is to be rejected. Most people reason by mood affiliation and use argumentation as a social tool, so this should not be a surprise. I think the "Overton window" is confusing cause and effect; it's the nature of reasonable positions to generate unreasonable fanatics at the tail ends. But if you pay attention to the loud fanatics at a given point of time, you find most of them do not shift any window but instead fall into irrelevance. I think that as RMS's software becomes less important, people will care less about what he has to say.
- glass- 12y agoGCC is a technically inferior compiler that has been deliberately neutered to enforce its license. When software has technical limitations to enforce its license that is DRM, ergo GCC is defective by design.
- arca_vorago 12y agoCan someone explain to me what all the hubub is about. As far as I understand it and even as RMS himself states, isn't this mostly about them trying to block clang/LLVM tie ins to the debugger more than anything else? I don't understand whats with all the gcc sucks attitude these days. It's worked for quite some time, and yes it's showing some age due to the lack of development so it has lagged behind others, but we should all be worried when people very influential in the GNU community start talking about why GCC is bad. I don't like this line of thinking at all. If GCC is behind, fork it and do what needs to be done to make it competitive.
- phkahler 12y ago>>Can someone explain to me what all the hubub is about. As far as I understand it and even as RMS himself states, isn't this mostly about them trying to block clang/LLVM tie ins to the debugger more than anything else? The "problem" RMS has with llvm is its non-copyleft license. And yes, the issue is that he doesn't want to support llvn with GNU tools. When LLVM started they used GCCs front end to compile C code until their own matured enough. So parts of GCC were being used to develop the middle and back ends of llvm. The LLVM ecosystem is systematically replacing the GNU toolchain with non-copyleft licensed versions and RMS does not want to support that in any way. >> I don't understand whats with all the gcc sucks attitude these days. It's worked for quite some time, and yes it's showing some age due to the lack of development so it has lagged behind others, but we should all be worried when people very influential in the GNU community start talking about why GCC is bad. I don't understand it either. GCC is still a great compiler. Developers seem to prefer the modular design of LLVM and they're probably right in that. Users like some of the features enabled by that design as well - IDE integration and cross compilation come to mind. GCC is starting to move, but slowly. >> I don't like this line of thinking at all. >> If GCC is behind, fork it and do what needs to be done to make it competitive. You make it sound like there are lots of compiler developers with time on their hands for open source development AND who share the licensing philosophy AND are unhappy with GCCs development path. Apparently there are not.
- Htsthbjig 12y ago"I don't understand it either. GCC is still a great compiler. Developers seem to prefer the modular design of LLVM and they're probably right in that." There are lots of things that are simply very hard to do with GCC, but are easily doable with LLWM. IDE integration is just one, because it has the ability to compile just lines(at least the Apple's version). Things we have done with LLVM: Millions of mollecules 3D paths' rendering. Automatic testing of software and hardware. Simulation of military vehicles doing all kinds of things. Digital crash test. Natural language(speech) understanding. Before LLVM doing all this took years, now it takes months or weeks. This exploits the ability of understanding languages of a compiler, but is not just compiling c or c++ like gcc does.
- wspeirs 12y agoI was under the impression that GCC would stick around as long as the Linux Kernel was in existence because there was a tight requirement for GCC to compile the Linux Kernel... well I was wrong! http://llvm.linuxfoundation.org/ http://llvm.linuxfoundation.org/ shows the status of getting the Linux Kernel to compile using CLANG... and according to the stats as of 1/28/2015 there are only 41 patches required to make this work. I wonder if any of the big distros will start compiling with CLANG instead of GCC?
- osw 12y agognu software considered harmful
- ForHackernews 12y agoAnyone see the header on Stallman's response? https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00488.html https://lists.gnu.org/archive/html/emacs-devel/2015-02/msg00... > [[[ To any NSA and FBI agents reading my email: please consider ]]] > [[[ whether defending the US Constitution against all enemies, ]]] > [[[ foreign or domestic, requires you to follow Snowden's example. ]]] He's such an adorable ideologue.
- phkahler 12y agoReading ESR tends to make me angry in a special way. I can understand people who prefer a BSD/MIT license over the GPL - they usually seem to understand the difference and claim the former are "more free" while kind of understanding the point of the later but disagreeing with its importance. But when I read ESR, he seems to have it in for the FSF and doesn't really seem to respect or even understand the philosophy at all. I've come to view him as a formerly-high-profile troll.
- GFK_of_xmaspast 12y agoRemember that ESR writes things like this: http://esr.ibiblio.org/?p=5001 http://esr.ibiblio.org/?p=5001 in all apparent seriousness.
- markhahn 12y agoReading stuff from ESR considered a waste of time.
- _pmf_ 12y ago> If the clang/LLVM people decide they want to eat GCC's lunch, they will do it They have about 5-10 architectures and about 40-50 architecture variants to catch up to GCC. It's doable, but it will take about the time it took GCC to get there, and the result will be that LLVM becomes the kind of unmaintainable mess that GCC is considered to be now. One would assume that the author of "The Cathedral and the Bazaar" would know a bit or two about the lifecycle of open source software.
- hga 12y agoAs I understand it, the counter arguments are: Not all of those architectures and variants are important going forward (I'd actually be very interested in lists of them). GCC was designed for and has been thoroughly maintained to be less maintainable (one of the major points of these recent prominent debates). C++ is more maintainable than C. (I don't know that I buy this at all, in fact, I'm about to dive into LLVM's source code to see if it could possibly prompt me to revoke my oath to never program in C++ and Perl again unless absolutely necessary :-). The last two, plus LLVM's Bazaar model of development in part enabled by those technological differences, means it won't be an unmaintainable mess if and when it grows out like that. I have no idea if this will be true. I'd like to hear from seasoned developers who are also seriously familiar with the LLVM architecture, development model and code base (per the above, I rather hope I won't become one of the latter).
- DannyBee 12y agoEric is right, but not for the right reasons. For starters, Apple's money is not the main driver of LLVM (In fact, publicly, Apple is not the #1 contributor anymore). Second, "but merely the fact that compiler technology has advanced significantly in ways that GCC is not well positioned to exploit. " is simply false In fact, that's exactly the problem for GCC: Compiler technology has not advanced roughly at all. GCC caught up to everyone else for the same reason. Time for a history lesson. About 14 years ago,a group of folks including Diego Novillo, Jeff Law, Richard Henderson, Andrew MacLeod, me, and Sebastian Pop (along with bug fixes/changes from a lot of others) sat around and build a "middle end" for GCC. Prior to that, GCC had a frontend, and a backend. The frontend was very high level (and had no real common AST between the frontends), the backend was very low level. There was nothing in between. We cherry picked the state of the art in compilers and research, and build a production quality IR and optimizer out of it. This research has not really changed that much in about 10-15 years. Most of the research these days focuses not on straight compiler opts, but on things like serious loop transforms, and helping runtimes (GPU, GC, etc), or dynamic languages. You can see all the tree ssa work here: https://github.com/gcc-mirror/gcc/blob/master/gcc/ChangeLog.tree-ssa https://github.com/gcc-mirror/gcc/blob/master/gcc/ChangeLog.... This covers only until the branch was merged. At that point, it was "not a piece of crap", but this was before people added all the stuff on top of this architecture. On top of that architecture, it took another few years to get good, and a few years after that to get really good. Bringing us to today. LLVM was started around the same time, but had less contributors back then. Essentially, you could view it as "instead of build something in between two really old parts, what could we do if we just redid it all". People thought it was a waste of time for the most part, but Chris Lattner persevered, found a bunch of crazy people to help him over the years, and here we are. Because you see, it turns out compiler technology has not really changed at all. So, algorithmically, LLVM and GCC implement the same optimization techniques in the middle of their compilers. Because there is nothing better to do. Just slightly different engineering tradeoffs. To put it another way: Outside of loop transforms, essentially static language compilers targeting CPU architectures are solved. We know how to do everything we want to do, and do it well. It just has to be implemented. So given enough time/effort, LLVM and GCC will produce as good of code as each other there. The question becomes "will they keep up with each other as engineering/tuning happens" and "who can generate great code faster". The problem for GCC on this front is three fold 1. The backend, despite being pretty heroic at this point, really needs a complete rewrite, but people value portability over fast code. LLVM, having started completely from scratch, has a modern, usable backend. They are not afraid to throw stuff away. 2. For any given thing you can implement, it's a lot easier to do it in LLVM than GCC, so, given time, LLVM will produce faster code because it takes less work to make it do so than it does to make GCC do so. 3. Because it was architected differently and more modernly, clang/LLVM are significantly faster at compiling than GCC. GCC can remove most if not all of the middle end time (and does), but it's still slow in other places, and that's really really hard to fix without fundamental changes (See #1)
- Elzair 12y agoHas anyone considered creating a new libre compiler suite in Rust? That would be pretty cool. I have wanted to do this, but I have so many other projects to work on.
- pekk 12y agoI strongly disagree with RMS on some issues (like Snowden) and I don't share his hard line on proprietary software either. But RMS is just a particular kind of animal. I respect the need for that animal in a diverse ecosystem and I respect the reasoning behind free software. In particular, I think gcc has played an essential role in providing free software to users because it is licensed under the GPL. The BSD license is great for less important things, but the moment giant corporations have engineered the whole "open source" ecosystem so that they can distribute forks of all the basic build tools without contributing changes to the public where we can see and influence them - that's the moment we've handed over the keys to the kingdom. You have to be pretty out of touch with history not to see that point. To hear the way HN talks about RMS, he is a nerdy, smelly, arrogant, technically ignorant Emmanuel Goldstein, representing everything we hate most about the nerdy computing world that pre-existed the current startup gold rush (but which, coincidentally, entirely enabled it and us). Now a large proportion of us here secretly harbor the belief that we are the next Steve Jobs, so we pine for the good old days when people like that made bank on companies whose business models were entirely based on platform lock-in. Because so few of us actually remember how fucked up it really was for all the users and programmers. Because we don't consider ourselves users and programmers, just temporarily embarrassed millionaires and Chief Engineering Architect Engineers. So it's no wonder that HN still doesn't understand the point of GPL. Just like most of Marin county now thinks measles is something to cultivate, like acidophilus.
- twic 12y ago> The BSD license is great for less important things, but the moment giant corporations have engineered the whole "open source" ecosystem so that they can distribute forks of all the basic build tools without contributing changes to the public where we can see and influence them - that's the moment we've handed over the keys to the kingdom. You have to be pretty out of touch with history not to see that point. So when in history has this actually occurred?
- ajarmst 12y agoI continue to be amazed at people buying into the ESR-authored consensual hallucination about his role and importance. His primary creative contribution to the community has been a fictional mythology starring himself.
- madmax96 12y agoIsn't RMS' main issue with LLVM that people can create proprietary plugins and those plugins benefit when LLVM benefits? How exactly is this different than if a company were to make proprietary extensions to Emacs and sell them? Does the Emacs license forbid against non-free extensions? Ultimately, it's not LLVM's problem if people create non-free extensions. You could argue all of Gnu/Linux is bad because some proprietary software runs on it. I don't think that's a route we want to take.
- copsarebastards 12y agoI agree with Eric Raymond that GCC probably can't beat Clang. However, I don't agree that this means we should just jump on the LLVM train. The world still needs GNU. And LLVM isn't GNU. The GNU community has historically held dominance in the compiler field, so this is an uncomfortable time. We can no longer rely on the popularity of GCC to keep GNU in the forefront. However, this doesn't mean we should just give up--I think the solution is to start again from first principles and build a better system, an alternative to GCC that is also released under the GPL. I'm not saying we should drop support for GCC. But we need to innovate: GCC became dominant because it was innovative and it lost dominance because it stopped innovating. LLVM isn't the only non-GNU competitor. It's telling that none of the major new languages (Go, Rust, Clojure, Scala) are released under the GPL.
- kibwen 12y agoThe implementations of new languages aren't being released as GPL because the process of introducing a new programming language is already a nearly insurmountable task. To this end, language authors seek every advantage they can get. Nobody's ever chosen a programming language by virtue of the fact that its implementation was GPL, but I can easily see people ruling out such a programming language out of fear that the use of such an implementation will infect their own code with GPL (I fully acknowledge that this fear is unwarranted if your licensing is set up properly, but it actually can be rather tricky to get right and most people are rightfully fearful of interpreting this sort of thing on their own). At the same time no developer of a fledgling language is going to worry about someone coming in and taking their permissively-licensed code without contributing back, because getting to the stage where someone cares enough to seriously fork your language already implies an enormous relative degree of success.
- bmuk 12y agoI tend to agree with RMS, at least on his philosophy of free software. That being said, I don't think adding LLDB support to emacs is a bad thing, and I don't think the rise of clang/LLVM will be a big hit to free software. As long as there are people who care about freedom, people will maintain GCC. Even if the worst case happens, and there is extreme fragmentation of proprietary patch-sets to LLVM, we can always still use GCC, or even still use the free parts of LLVM/clang. While there is some issue with fragmentation of the developer community, I see this as a non-issue. These things generally work themselves out through the natural ebb and flow of chaotic systems (just like the economy is largely self-regulating). We can always still use GCC. I don't really see where the issue is, am I missing something?