On 5/10/2021 3:45 PM, abebeos via Gcc-patches wrote:
I've described this in my message here: https://gcc.gnu.org/pipermail/gcc-patches/2021-May/569913.html The summary is possibly * I identified via necessary week-long work a (shelved) patch as valid for (re)use. * The gcc project(members) simply downplayed my week-long efforts to essentially "nothing". * Issue-author, patch-author and other gcc participants kept silence when the voting-process was rigged. * (and some other things, like e.g. missing complaint-addresses/procedures which enable "wild-west" abuse of workers). See, I do hard/soft/firmware, but before that, I setup stable reproducible dev-environments (which gcc lacks, at least for avr). Then I try to validate/reuse/extend existent results. Only then, I go to implement own solutions. This is a usual process, nothing special for professionals. But here comes the bomb: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92729#c55 "You have no claim in this whole effort. You just tried to copy someone else's work."
This comment is from the person who set up the bounty. Your issue is with him and/or bountysource. The GCC project does not control or directly influence the bountysource program.
Jeff
