This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/61315] wide-int.cc cannot be built by darwin system compiler


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61315

--- Comment #12 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
(In reply to Jack Howarth from comment #6)
> I would also add that you are playing with fire here. Currently no company
> has a motivation to expend money or resources for fortran development on
> llvm as long as FSF gcc is buildable. If you start removing competing
> compilers from bootstrapping FSF gcc, it is much more likely that someone
> will fund such a llvm-based fortran compiler project. You may get some
> short-term satisfaction from walling off FSF-gcc from clang, the long-term
> outcome for the FSF gcc project might not be so happy.

Is any company spending money on GCC Fortran development? That would be awesome
if it were true!

I also doubt that somebody will decide to fund a whole llvm-fortran compiler
instead of simply installing GCC 4.2, which should still be able to bootstrap
GCC trunk. It would be a strange business decision, unless the goal was to
build a proprietary compiler by leeching off volunteer unpaid developers. That
would make sense then.

Since you are offering advice, let me humbly offer some back to you: Why not
instead of starting a confrontation with Andrew and invoking some
strange-sounding threats, you propose a patch to fix the problem? That seems to
me much more constructive. Moreover, you don't even need to convince Andrew (or
me), you just need your patch to be approved by one of the Global Reviewers (or
the maintainers responsible for that part of the compiler). See
gcc/MAINTAINERS. I don't see your name in that list, perhaps it would be a good
time to start the steps to add it: https://gcc.gnu.org/contribute.html

BTW, having a user-base without developers coming out of that user-base is
useless. If no one from apple-darwin is interested in developing GCC, then it
doesn't matter how big the user base is: GCC for apple-darwin will not get
developed by magic gnomes (or by people that don't even own Apple hardware). So
perhaps it would be in your own interest to do a bit of recruiting in the
apple-darwin camp.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]