Hi Paolo,> I would also avoid testcases using volatile. Smaller code on these testcases > is often a sign of miscompilation rather than optimization. For example, > http://embed.cs.utah.edu/embarrassing/src_harvested_dec_09/076389.c is > miscompiled on GCC 3.4 and SunCC 5.10.Yeah, there are definitely several examples where small code is generated by miscompilation, especially of volatiles. However I would prefer to leave these testcases in, unless there is a strong feeling that they are too distracting. They serve as poignant little reminders about how easy it is to get volatile wrong... John
> However I would prefer to leave these testcases in, unless there is a > strong feeling that they are too distracting. They serve as poignant > little reminders about how easy it is to get volatile wrong...They skew the results in favor of the less careful compilers so they are more than simply distracting, they are unfair. -- Eric Botcazou
On Thu, Dec 17, 2009 at 19:54, Eric Botcazou <ebotcazou at adacore.com> wrote:>> However I would prefer to leave these testcases in, unless there is a >> strong feeling that they are too distracting. They serve as poignant >> little reminders about how easy it is to get volatile wrong... > > They skew the results in favor of the less careful compilers so they are more > than simply distracting, they are unfair.Yes, that was my point. If you want to make a separate section for volatile, that would indeed be helpful. Paolo