On 05/22/2012 11:55 AM, Paolo Carlini wrote:
FAIL: gcc.dg/opts-1.c (internal compiler error) FAIL: gcc.dg/opts-1.c -fno-abi-version (test for errors, line ) FAIL: gcc.dg/opts-1.c -fno-lto-compression-level (test for errors, line ) FAIL: gcc.dg/opts-1.c -fno-tree-parallelize-loops (test for errors, line ) FAIL: gcc.dg/opts-1.c -Wno-strict-overflow (test for errors, line ) FAIL: gcc.dg/opts-1.c -Wno-strict-aliasing (test for errors, line ) FAIL: gcc.dg/opts-1.c (test for excess errors) FAIL: gcc.dg/opts-5.c (internal compiler error) FAIL: gcc.dg/opts-5.c (test for errors, line ) FAIL: gcc.dg/opts-5.c (test for excess errors) FAIL: gcc.dg/opts-6.c (internal compiler error) FAIL: gcc.dg/opts-6.c (test for errors, line ) FAIL: gcc.dg/opts-6.c (test for excess errors)
That all looks like diagnostics about options that don't work properly together, much like the objc issues. I think it makes sense to switch all such diagnostics over to BUILTINS_LOCATION, because we do know the location of the thing we're complaining about: it's on the command line.
Jason
