These warnings have driven me insane for years:

blah.cc:1: error: too many arguments to function ‘void a(int)’
blah.cc:7: error: at this point in file

I always end up jumping to line 1 in the file.  I glance at the message and
line number in the first line, and I'm jumping to that line number before my
brain has really processed which error message it is.  This is inherently
something I can't learn to work around without deliberately slowing down my
workflow (a mental pipeline stall?).

The line number next to the error should be the one causing the error; any
additional, related lines should come *after*.  This is much better:

blah.cc:7: error: too many arguments to function ‘void a(int)’
blah.cc:1: error: declared here

This also makes it consistent with the C version of this error.


-- 
           Summary: "at this point in file" warnings are upside down
           Product: gcc
           Version: 4.4.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: glenn at zewt dot org
  GCC host triplet: i486-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43126