This weekend I discovered a particularly nasty bug in gcc 4.4 where gcc
would mistakenly optimize out important sections of code
when it encountered a particular trick used in a ton of places inside
Evolution (EDList and pretty much everywhere custom single-linked lists
are used inside at least Camel and likely other places as well).

A temporary solution is to pass the -fno-strict-aliasing argument to gcc.

Unfortunately, the gcc developers claim that this is not a bug:


Evolution-hackers mailing list

Reply via email to