public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rainer@emrich-ebersheim.de" <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 11:51:00 -0000 [thread overview] Message-ID: <bug-64972-4-KYcHNeGsu6@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 #8 from Rainer Emrich <rainer@emrich-ebersheim.de> --- I'm testing the following on x86_64-w64-mingw32 at the moment. Index: oacc-parallel.c =================================================================== --- oacc-parallel.c (Revision 221607) +++ oacc-parallel.c (Arbeitskopie) @@ -99,8 +99,9 @@ GOACC_parallel (int device, void (*fn) ( gomp_fatal ("num_workers (%d) different from one is not yet supported", num_workers); - gomp_debug (0, "%s: mapnum=%zd, hostaddrs=%p, sizes=%p, kinds=%p, async=%d\n", - __FUNCTION__, mapnum, hostaddrs, sizes, kinds, async); + gomp_debug (0, "%s: mapnum=%ld, hostaddrs=%p, sizes=%p, kinds=%p, async=%d\n", + __FUNCTION__, (unsigned long) mapnum, (void *) hostaddrs, + sizes, kinds, (int) async); select_acc_device (device); @@ -178,8 +179,9 @@ GOACC_data_start (int device, size_t map bool host_fallback = device == GOMP_DEVICE_HOST_FALLBACK; struct target_mem_desc *tgt; - gomp_debug (0, "%s: mapnum=%zd, hostaddrs=%p, sizes=%p, kinds=%p\n", - __FUNCTION__, mapnum, hostaddrs, sizes, kinds); + gomp_debug (0, "%s: mapnum=%ld, hostaddrs=%p, sizes=%p, kinds=%p\n", + __FUNCTION__, (unsigned long) mapnum, (void *) hostaddrs, + sizes, kinds); select_acc_device (device); Index: target.c =================================================================== --- target.c (Revision 221607) +++ target.c (Arbeitskopie) @@ -439,8 +439,8 @@ gomp_map_vars (struct gomp_device_descr was missing. */ size_t size = k->host_end - k->host_start; gomp_fatal ("present clause: !acc_is_present (%p, " - "%zd (0x%zx))", (void *) k->host_start, - size, size); + "%ld (0x%lx))", (void *) k->host_start, + (unsigned long) size, (unsigned long) size); } break; case GOMP_MAP_FORCE_DEVICEPTR:
next prev parent reply other threads:[~2015-03-24 11:40 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 [this message] 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 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-KYcHNeGsu6@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: linkBe 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).