On 24.01.2013 11:33, Xi Wang wrote:
> I'm sending three smaller patches for review, which try to fix icc
> and pathscale (mis)compilation problems described in my last email.
These patches look ok at a quick glance, but how do we ensure this kind
of problems don't crop back again in the future? Does icc give a warning
about these? Do we have a buildfarm animal that produces the warnings?
If we fix these, can we stop using -frapv on gcc? Is there any way to
get gcc to warn about these?
- Heikki