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

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch

--- Comment #43 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Roger Weber from comment #42)
> I posted the latest duplicate of this bug, and I don't know anything about
> how gcc works. I am very grateful for the hard work you guys put into this,
> but just looking at the data. This bug was first reported 13 years ago - and
> I think it's a pretty important one as one can easily make a mistake with
> initialization.

GCC is very large and growing and the number of GCC developers is very very
small and not growing. There are thousands of open bugs, thus developers need
to prioritize. If something was truly pretty important, someone would have
stepped up (or paid someone) to fix it. There is a 60 lines patch that fixes
most of the testcases here and could serve as inspiration to solve the rest.
The person who produced the patch left the work unfinished. Someone needs to
finish it:
https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps

It is a simple as that.

Reply via email to