------- Comment #39 from pinskia at gcc dot gnu dot org 2006-09-26 15:49 ------- (In reply to comment #37) > Your point?
That aliasing rules in C is older than my girl friend and that they have been around for a lot longer than people give credit for. > Fact: strict aliasing horrifies most software developers. Fact: most developers are taught right to begin with. But is that a GCC issue, no. Fact: aliasing rules in C are easy to understand if you don't take pointer types into account. > The wording in a seriously expensive ISO document doesn't > change the simple fact that people don't write code that way. > Books intended to teach the language don't mention this > "feature" of the language. I don't just mean "Learn C in > 5 days", but college textbooks as well. Well those books should be punished in the open market but is that a GCC issue, no. And if those books are not mentioning this problem, well someone should complain to them and not to GCC that they don't get something correct. > I know. I'm perfectly clear on that. You don't need to remind me. It is to remind all the people who look into this bug later on to see why their code is wrong or correct. Anyways embedded people should be using type based aliasing to their benifit instead of working around it as type based aliasing can help code size and speed of their program. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28778
