Christian Svensson
2014-12-30 11:43:17 UTC
Hi,
You might recognize me from e-mails containing such words as "upstreaming",
"binutils" and "GCC".
I have not kept myself updated in the latest of OpenRISC for the last
months, so forgive me if I've missed some new developments in any of the
areas below.
I feel like I owe it to the community and the contributors to write this
public statement where we are, so here you go.
This is long overdue status update on the GCC upstreaming effort.
Back this last summer I sent out an email to all the contributors to our
GCC port to ask them to assign copyright to GNU. I also asked some people
to take a look at our GCC patches and the initial reaction was good (Thanks
Giuseppe!).
As for the assignment:
A few months later I verified the assignment status with the FSFs GNU
administration.
All the authors have successfully assigned copyright, except one whom I
have successfully reached out to but since then lost contact with. If
someone knows a Mr. M****z B**s***r and can ask him to assign copyright,
I'd be most delighted.
In any case, if anyone feels like they want to try to reach out to our last
contributor please contact we and I will supply the contact details that I
know of.
As for the code review:
We need to find a GCC code reviewer. The GCC folks informed me that we need
someone who is a 'global reviewer' and we probably need to convince someone
to do this for us, as it is a bit of work involved - understandably.
As for the code status:
Last time I tried to run the GCC testsuites I got quite the number of
failed test cases. This may or may not be issues in everything from GCC,
glibc and even Linux. Or it might be that the testcase is stupid for
OpenRISC and should be disabled. This said, I'm not convinced that we will
get a go ahead given that we haven't got a 100% pass yet. Having some
continuous testing here would be sweet if anyone would like to set that up
- or at least some way of tracking the regressions (we used to have this on
the old wiki but I don't think it has been updated).
These three blockers described above (assignment, review and testsuites)
are all too much for me to handle on my own, and that's largely why it
hasn't progressed the last couple of months.
The biggest hit on me personally would be the assignment part, as if we can
get that done we might be able to push the patches as extra patches in for
example Debian.
It's quite sad if we cannot finish it, given that we're so close. The step
where a lot of people were nervous about was the assignment, which is
really really close.
Let me know if you wonder something or want to help push this beast
forward.
Thanks for reading!
Christian
You might recognize me from e-mails containing such words as "upstreaming",
"binutils" and "GCC".
I have not kept myself updated in the latest of OpenRISC for the last
months, so forgive me if I've missed some new developments in any of the
areas below.
I feel like I owe it to the community and the contributors to write this
public statement where we are, so here you go.
This is long overdue status update on the GCC upstreaming effort.
Back this last summer I sent out an email to all the contributors to our
GCC port to ask them to assign copyright to GNU. I also asked some people
to take a look at our GCC patches and the initial reaction was good (Thanks
Giuseppe!).
As for the assignment:
A few months later I verified the assignment status with the FSFs GNU
administration.
All the authors have successfully assigned copyright, except one whom I
have successfully reached out to but since then lost contact with. If
someone knows a Mr. M****z B**s***r and can ask him to assign copyright,
I'd be most delighted.
In any case, if anyone feels like they want to try to reach out to our last
contributor please contact we and I will supply the contact details that I
know of.
As for the code review:
We need to find a GCC code reviewer. The GCC folks informed me that we need
someone who is a 'global reviewer' and we probably need to convince someone
to do this for us, as it is a bit of work involved - understandably.
As for the code status:
Last time I tried to run the GCC testsuites I got quite the number of
failed test cases. This may or may not be issues in everything from GCC,
glibc and even Linux. Or it might be that the testcase is stupid for
OpenRISC and should be disabled. This said, I'm not convinced that we will
get a go ahead given that we haven't got a 100% pass yet. Having some
continuous testing here would be sweet if anyone would like to set that up
- or at least some way of tracking the regressions (we used to have this on
the old wiki but I don't think it has been updated).
These three blockers described above (assignment, review and testsuites)
are all too much for me to handle on my own, and that's largely why it
hasn't progressed the last couple of months.
The biggest hit on me personally would be the assignment part, as if we can
get that done we might be able to push the patches as extra patches in for
example Debian.
It's quite sad if we cannot finish it, given that we're so close. The step
where a lot of people were nervous about was the assignment, which is
really really close.
Let me know if you wonder something or want to help push this beast
forward.
Thanks for reading!
Christian