[Bug c++/31505] [4.3 Regression] Canonical types failures

["bangerth at dealii dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #10 from bangerth at dealii dot org  2007-04-09 15:23 -------
Great, thanks. Hopefully someone approves the patch soon.

Talking about canonical types: I think the idea of only issuing a warning
in cases like the current one is a really bad idea. Warnings are meant for
things where the programmer did something dubious (if correct) and that
can be silenced by adjusting the source code. On the other hand, what we
have here is a compiler whose internal data structures have become corrupted.
That's pretty much the definition of what we use ICEs for, and I would urge
you to reconsider the idea of using a warning instead.

Does it matter? I do think so. For example, I found this one by actually 
looking at the log files of my automated compile jobs. It showed a successful
compilation, rather than a failure, because a warning still makes 'make' go
on as if nothing had happened. I'm sure canonical type failures would be
found quicker if their effect was more drastic, because it makes people
look for the place where something goes wrong.

Best
  Wolfgang


-- 


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