This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: const volatile behaviour change in GCC 7


> On Sep 22, 2016, at 6:17 AM, David Brown <david@westcontrol.com> wrote:
> 
> ...
> Your trouble is that your two pointers, cur and end, are pointing at
> different variables.  Comparing two pointers that are independent (i.e.,
> not pointing to parts of the same aggregate object) is undefined - the
> compiler can assume that these two external objects could be anywhere in
> memory, so there is no way (in pure C) for you to know or care how they
> are related.  Therefore it can assume that you will never reach "cur ==
> end".

Would making them intptr_t instead of pointers fix that?

	paul


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]