|
From: Doug E. <dj...@go...> - 2008-07-11 05:16:10
|
On Wed, Jun 18, 2008 at 6:00 AM, Alan Jenkins <aj...@st...> wrote: >> Yes .. known problem. I think you can persuade gcc not to do the >> inlining if you give it -mno-inline-all-stringops. That would allow >> you to still use -O and above. I'd be interested to know if this >> helps. >> > No, it still generates the same invalid read error. > > I think -mno-inline-all-stringops is the default. Looking at the > manpage, GCC will always inline in my case, because it knows my string > is aligned. My string is a variable length array at the end of a C > structure, and the previous field is a pointer. So I don't think I can > disable this specific optimisation. -fno-builtin but it is a sledgehammer |