On Wednesday 12 April 2023 10:53:32 Nick Clifton wrote: > Hi Pali, > > > > Hello! Just for a record, I filled individual issues to bugzilla: > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30004 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30139 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30140 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30141 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30142 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30143 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30144 > > > https://sourceware.org/bugzilla/show_bug.cgi?id=30145 > > > > Hello! Should I do something more regarding these issues? > > Hitting me with a big hammer ? > > *sigh* I was really hoping that someone else would step up to look at these > issues as I am not a Windows expert.
Hello! Sorry I did not want to bother you. I sent email to mailing lists, hoping that some Windows expert look at it. > It looks like the first one (30004) has been fixed, and 30140 may have been > resolved - assuming that you agree with the explanation in comment #2. But > the others all need addressing. I will try to make time for them in the next > few weeks. And something was moved to gcc. I was in impression that this is just one "big" project, but I see that gcc and binutils are like more separated projects with separate bug trackers. And I'm not always sure which code part belongs to which project... So excuse me if I put something into incorrect issue tracker. > If you do have any suggestions for fixes to any of these problems, please do > feel free to add them to the relevant bug reports. Of course! I will put comments into tickets and also test new patches. > Cheers > Nick > > >
