This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Why not contribute? (to GCC)
Joel Sherrill:
I don't know how divergent rdos from any other OS that is
not self-hosted and is cross-compiled but there shouldn't
be 100s or 1000s of patches required to support an OS on gcc
unless you have a divergent object format or are including
a new CPU.
Also you haven't mentioned two major issues that are
not "patch" related.
(1) Did you arrange for a maintainer for the rdos target?
(2) Did you submit test results with the port?
(3) Has copyright assignment paperwork been dealt with?
I maintain the *-rtems* targets (~12 architectures) and there
just isn't much special to them in contrast to the large amount of
code that just works fine with a bit of OS specific configuration
and glue.
Not to pick but from Google'ing the mailing list, I just see you
asking questions. I didn't find code being submitted.
The primary issue I had was that some basic configuration was
never updated to GCC (libtool). Because this was the place where the
targets and stuff was defined, it was not even possible to submit specific
patches in the first place, because they would fail without this refresh.
And speaking from experience, if you submit code and it doesn't
get reviewed and merged. Ask again. The submitter cares a lot
more about it than anyone else and that's just the nature of the
game. If you don't care enough about your area to follow up, why
should anyone else?
I think I posted pings.
As for the steps above, nobody requested me to fill out the
copyright assignment, and neither about maintainer for rdos
target.
The 100s of patches related to libc (in this case newlib), not
to gcc. I mixed up those. However, it was not possible to submit
the patches to newlib either until the GCC patches had been
applied.
Leif Ekblad