On 10/12/2017 10:49 PM, Oren Ben-Kiki wrote:
On Fri, Oct 13, 2017 at 4:47 AM, Martin Sebor <mse...@gmail.com <mailto:mse...@gmail.com>> wrote: My organization was particularly focused on warnings so I'm quite familiar with the challenges you're hoping to overcome. I figured I wasn't the only one :-) But it is good to hear from others. My best advice is to either write a script to determine the options the target compiler supports and use only those, or write a compiler driver that handles this for you (it doesn't relieve you of the tedious task of researching all the options and hard wiring them into the driver(*)). Yes, this is probably the best one can do right now. This isn't to say that GCC shouldn't make it easier, but as you note, even if and when it does, it will take years before the solution is universally available. Making the world a better place for the next generation is a worthy goal ;-) [*] We wrote a script scrape those off the online HTML manual and create a "database" mapping options to GCC versions they were introduced in (or first documented in, as not every option always gets documented as it gets added). Sounds interesting! I don't suppose this driver is available as a separate standalone tool?
Ours was a proprietary script but I'm pretty sure sure I've seen similar compiler wrappers in open source. If I'm not mistaken projects like DistCC and the no longer maintained (AFAIK) Trolltech TeamBuilder come with drivers that do similar things. There are bound to be others. Good luck! Martin
