This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
At this point, I wonder what is wrong with Bugzilla, that those programmers don't fill a proper bug report. If there is a problem with GCC, that is so annoying to somebody, I think that at least developers could be informed about it via their standard channels of communication. If there is a specific problem, at least it can be analysed properly and perhaps some actions could be taken to fix it. If the problem is indeed _that_ big (usually, it is not!), then a workaround could be suggested - and this bug, together with a workaround is documented in bugzilla for others, until the problem is properly solved (usually with a testcase). I guess that these persons don't know that bugreports are extremmely important for the development of gcc. The users themself are actaully a QA department of open source development;)I do know this: Many, many scientific and mathematical programmers find GCC frustrating and annoying, and most of those folk know far more about numbers than I do. I wish more of these people would feel comfortable posting to the GCC list, rather than sending private e-mails to my inbox.
I would call it an atmosphere of brainstorming. Different opinions and different point of views. The only problem is, that words can be different if people sit 3000 km/miles/whatever apart ;)However, the atmosphere of GCC development is... well, let's just say that my investment in asbestos underware has not been wasted. ;)
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |