This commit includes fixes to undefined behavior caught by this
attribute.  The following changes have been made:

- 0x%0.8p is changed to %016 PRIxPTR. Both 0 and . have undefined behavior with
  p.  Additionally, %p already prints 0x with both gcc and clang.  This
  results in a small output change:

    void *x = (void *)0x1234;
    void *y = (void *)0x1234567890abcdef;

    printf("|%0.8p|\n", x);
    printf("|%0.8p|\n", y);

    printf("|%016" PRIxPTR "|\n", reinterpret_cast<uintptr_t>(x));
    printf("|%016" PRIxPTR "|\n", reinterpret_cast<uintptr_t>(y));

  prints:

    |0x00001234|
    |0x1234567890abcdef|
    |0x0000000000001234|
    |0x1234567890abcdef|

- %d used for GLintptr, GLsizeiptr, EGLTime and EGLnsecsANDROID is
  changed to %llu and the relevant argument is cast to unsigned long
  long.  This is due to these types being typedefs to unknown types (on
  Linux for example, these are unsigned long, and my guess would be
  unsigned long long on Windows where long is 32 bits).
- %llu is used for GLuint64, which could be unsigned long (as is on
  Linux).  Those arguments are cast to unsigned long long.
- %p is used for some EGLNative types, but those types may not be a
  pointer.  Those arguments are cast to uintptr_t and printed as above.

Bug: angleproject:2928
Change-Id: I63e9e998c72701ce8582f1ebf25d6374be9090e4
Reviewed-on: https://chromium-review.googlesource.com/c/1289232
Commit-Queue: Shahbaz Youssefi <syoussefi@chromium.org>
Reviewed-by: Yuly Novikov <ynovikov@chromium.org>