https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67429
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> --- (In reply to Steve Kargl from comment #5) > > > > Please read comment 0. > > > > I read comment #0. > > THERE IS NO CODE THERE. > > THERE IS NO CODE ATTACHED TO THIS PR. > > One needs to go to PR65045 to get the code > that is causing the error message. Ergo, > this is a duplicate of PR65045. > > When PR65045 is fixed. The issue with the > error message should be addressed then. Steve, This is a problem that has surfaced with the change to the gcc error handling. Rainer Orth has encountered it on Solaris and it caused me to hold back on my patch for pointer function assignment. The patch for PR65045 is the simplest manifestation that I have found. I am very grateful to Dominique for posting this PR because the problem has been driving me crazy. I assumed that it was my patches that were wrong. However, Dominique proved by going through different revisions that the December 2014 patches to error.c are the culprits. Go easy on us both - it's getting a bit late here :-) Cheers Paul
