public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/64972] [5 Regression] Build failure in libgomp for i686-w64-mingw32 target after latest merge from gomp-4_0-branch
Date: Tue, 24 Mar 2015 16:21:00 -0000	[thread overview]
Message-ID: <bug-64972-4-t020J8DrS4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64972-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64972

--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I wouldn't call %zd gnu-style, as it is POSIX.
Anyway, libgomp already uses inttypes.h, but only conditionally:
#ifdef HAVE_INTTYPES_H
      fprintf (stderr, "  GOMP_SPINCOUNT = '%"PRIu64"'\n",
               (uint64_t) gomp_spin_count_var);
#else
      fprintf (stderr, "  GOMP_SPINCOUNT = '%lu'\n",
               (unsigned long) gomp_spin_count_var);
#endif
So, if you'd like to do the same (but then cast to uint64_t and use PRIu64,
dunno how portable is PRIuPTR compared to PRIu64), that is also an option,
but IMNSHO not worth the trouble.
All these messages are unimportant OpenACC debugging messages or a fancy abort
that will very likely not have sizes of anything > 2GB - trying to offload 2GB+
of data to offloading device in one chunk is hardly a case to worry about.


  parent reply	other threads:[~2015-03-24 15:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-08 13:43 [Bug libgomp/64972] New: " erik-gcc-bugzilla at vanpienbroek dot nl
2015-02-11 15:54 ` [Bug libgomp/64972] " ktietz at gcc dot gnu.org
2015-03-24  7:49 ` rainer@emrich-ebersheim.de
2015-03-24  8:01 ` [Bug libgomp/64972] [5 Regression] " ktietz at gcc dot gnu.org
2015-03-24  8:11 ` ktietz at gcc dot gnu.org
2015-03-24 10:57 ` rainer@emrich-ebersheim.de
2015-03-24 11:01 ` jakub at gcc dot gnu.org
2015-03-24 11:43 ` rainer@emrich-ebersheim.de
2015-03-24 11:51 ` rainer@emrich-ebersheim.de
2015-03-24 15:05 ` mikpelinux at gmail dot com
2015-03-24 16:20 ` ktietz at gcc dot gnu.org
2015-03-24 16:21 ` jakub at gcc dot gnu.org [this message]
2015-03-24 18:52 ` tschwinge at gcc dot gnu.org
2015-03-24 20:18 ` jakub at gcc dot gnu.org
2015-03-24 20:37 ` ktietz at gcc dot gnu.org
2015-03-24 20:56 ` jakub at gcc dot gnu.org
2015-03-25 13:23 ` rguenth at gcc dot gnu.org
2015-03-25 15:41 ` ktietz at gcc dot gnu.org
2015-03-25 15:43 ` ktietz at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-64972-4-t020J8DrS4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).