On 05/19/2010 04:10 PM, Mauro Carvalho Chehab wrote: > H. Peter Anvin wrote: >> Recently, we have seen an increasing number of problems with gcc 3.4 on >> x86; mostly due to poor constant propagation producing not just bad code >> but failing to properly eliminate what should be dead code. > > I don't see any problem, as, if people are using gcc3, they are probably > not interested on the bleeding edge kernel. > > However, if the problems are just performance/dead code removal, I would > just add a big warning if someone tries to compile x86 with it. I don't > like very much the idea of having different minimum gcc requirements > for each architecture, except if gcc is producing a broken code. > > Currently,Documentation/Changes list just a common minimal list for > everything - although the text describing gcc say that the "version > requirements" may vary for each CPU type. > We already have different gcc version requirements, whether or not they're written down is another matter... -hpa -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|