This is the mail archive of the gcc@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]

Re: GCC 3.0 for Solaris x86


> Date: Wed, 20 Jun 2001 17:32:58 -0400 (EDT)
> From: Michael Lee <ml@gbridge.com>
> To: gcc@gcc.gnu.org

> I take it that there is no specific plan to support Solaris x86 by the GCC
> group other than waiting for someone to contribute code.  Is that correct?

I'll give my version of this answer...  Hopefully it will explain a
bit more...

gcc is maintained by a bunch of people that donate their time on a
volunteer basis to the FSF.  The FSF doesn't (nor should the general
public) have any expectations that any particular bit of work will be
done or not by the gcc team, rather if someone wants work done, they
have to find someone willing to sign up for the effort.  Generally, we
don't press people and sign people up, as they are donating their
time, and this makes is somewhat less fun (more like real work).  At
times, for example, during a release, we will do this.  Usually we
just ask for volunteers to sign themselves up for work items that we
develop.  If no one wants to take on responsibility for a work item,
then we remove the task from the list of things to do.

The best way to approach getting things fixed, would be to point out
the critical problems you are having on the bugs list, and then see if
they get fixed.  If they don't get fixed (after some amount of time),
then ask if anyone works on the problem area that you're interested
in, and if they've had a chance to look at the bug (give an html link
for the bug report).

Nothing is supported in gcc, because no one is paid to offer support.
However, this doesn't mean that bug reports aren't addressed and the
problems aren't resolved.  A great deal of people spend countless
hours supporting gcc.

If you want `support' there are individuals and companies that can
offer commercial support to you.  You say jump, they take you're
money, and then they jump.  I'd recommen going this approach if you
have company dollars at stake, or if you have the need.  Quite a lot
of work that happens on gcc, is because someone, somewhere is paying
for it.

And last, If you have some time and the desire you can help support
yourself by tracking down when the problem was introduced, gather
state about it, and asking for ways to support yourself.


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