Joern Rennecke <amyl...@spamcop.net> writes: >> By the way: Are there better places to ask such questions like in gcc-help? > > If you actually need a new gcc backend and want it to be done well. you > should instruct an experienced contractor to do it for you, or hire an > in-house expert. > > Your question reveals that you are not familiar with gcc, and further > suggests that you are trying to implement a new backend alone or in a team > lacking a gcc expert. This is likely to either fail or result in a > backend of substandard quality which will never make it into the FSF > repository. > You might eventually (after several years) improve and come up with a > proper backend, but you will likely pick up the necessary skills more > quickly if you start out with something less ambitious, like improving > an existing backend, and have your patches peer-reviewed on the gcc > mailing list. > Or if you directly cooperate in implementing your new backend with someone > who already has the necessary experience. > > Thus, although your orginal question is valid in principle on this list, > answering is not likely to really help you, nor are you likely to help > the GCC community in the forseeable future if you are working on an > over-ambitious project project. > Thus, there is little incentive for anybody knowledgable reading this > list to answer this question. > > If the same question had been asked in a different context, e.g. a small > patch to the x86 backend in order to support some new and exciting linux > application, the odds of getting a timely response would have been higher.
This seems a little bit unfair to me. We do have volunteers, and we should encourage them. Our internals documentation is very weak. I never saw the original question, or I would most likely have answered it. It's of course true that context helps, and your answer to the question seemed like a good one. Ian
