Date: Mon, 25 Jul 2016 09:20:21 +0000 From: bugzilla-noreply@freebsd.org To: perl@FreeBSD.org Subject: [Bug 210837] lang/perl5.22 (and related?): ext/re/re_exec.c has long long format matched up with long argument Message-ID: <bug-210837-14331-gOIuUTqNuE@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-210837-14331@https.bugs.freebsd.org/bugzilla/> References: <bug-210837-14331@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210837 --- Comment #11 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mathieu Arnold from comment #8) I still have more to do but I got a little time to see what the compile messages were like on armv6 (an ILP32 FreeBSD architecture) after applying = the patch to the 5.22 source. I did not see any warnings about odd mixes of 32-bit types and 64-bit types between formats and values/storage or other such. BUT: For armv6 there are format warnings for 32-bit types int vs. unsigned long (31-bit precision and sign bit vs. 32-bit precision and no sign bit). Vario= us files get the same messages. I list the message a little later below. If the types stay int and unsigned long on amd64 it would end up being 32-b= it (int) vs. 64-bit (unsigned long). So this could then be more than a signed = vs. not issue. But something might auto adjust so I need to try amd64 directly. That will not be tonight. ./const-xs.inc:1451:21: warning: format specifies type 'int' but the argume= nt has type 'line_t' (aka 'unsigned long') [-Wformat] COP_FILE(cop), CopLINE(cop)); ^~~~~~~~~~~~ ../../cop.h:529:21: note: expanded from macro 'CopLINE' #define CopLINE(c) ((c)->cop_line) ^~~~~~~~~~~~~~~ ./const-xs.inc:1456:50: warning: format specifies type 'int' but the argume= nt has type 'line_t' (aka 'unsigned long') [-Wformat] COP_FILE_F " line %d\n", sv, COP_FILE(cop), CopLINE(cop)); ~~=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20 ^~~~~~~~~~~~ %lu ../../cop.h:529:21: note: expanded from macro 'CopLINE' #define CopLINE(c) ((c)->cop_line) ^~~~~~~~~~~~~~~ Side note: There was the message: op.c:13436:35: warning: comparison of constant 2251799813685247 with expres= sion of type 'PADOFFSET' (aka 'unsigned long') is always false [-Wtautological-consta nt-out-of-range-compare] if (intro && base > ~~~~ ^ I do not know if 5.24 gets this or not. Nor if this is an okay "always fals= e" or not. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-210837-14331-gOIuUTqNuE>