--- Comment #5 from contact at philipashmore dot com 2010-08-07 02:01
---
In my projects I add "-isystem ${top_srcdir}", the top source directory being
v3c.
This way, the examples can
#include
Just like code you might develop yourself using treedb.
I do a lot of
gcc -E -c a.c .
--- Comment #4 from rguenth at gcc dot gnu dot org 2010-08-06 13:55 ---
(In reply to comment #3)
> Maybe I should add that the 0.6.0-beta1 release in GIT passed uintptr_t -
> sized
> structures by value and the compiler spotted the aliasing, which is why I
> introduced the pointer -> ui
--- Comment #3 from contact at philipashmore dot com 2010-08-06 13:52
---
Maybe I should add that the 0.6.0-beta1 release in GIT passed uintptr_t - sized
structures by value and the compiler spotted the aliasing, which is why I
introduced the pointer -> uintptr_t -> pointer hacks to beg
--- Comment #2 from contact at philipashmore dot com 2010-08-06 13:37
---
It's exactly what I tried first - I know there are obvious cases as per your
"frequently reported bugs" section.
I wanted the compiler to tell me where the aliasing was occurring in these and
in
any less obvious p
--- Comment #1 from rguenth at gcc dot gnu dot org 2010-08-06 10:28 ---
We need a testcase. Also please try -fno-strict-aliasing if you know the
code is bogus.
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
