Date: Wed, 06 Jul 2016 12:13:14 +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-ZqVnp6gjbm@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 #10 from Mark Millard <markmi@dsl-only.net> --- (In reply to Mathieu Arnold from comment #8) I have not reviewed the all the other 32-bit vs. 64-bit issues addressed by 73e8ff0004522621dfb42f01966853b51d5522a6 yet. But it should help all TARGET_ARCH's with long being 32-bits and long long being 64-bits. I'll note that building for i386 should be much like building for armv6 for these issues: 32-bit long's and 64-bit long long's, all little endian. I'd expect the same warnings-status form the 2 targets. They are not as extreme as powerpc (big-endian) operationally but I'd expect powerpc (non-64) builds to also get the same warnings status as i386 and ar= mv6. If you want to see warnings generation yourself and you can target i386, th= at should work for seeing the 32-bit long vs. 64-bit long long sorts of issues= in compiler reports. No armv6 or powerpc needed. If I get some time I'll see if I can try a build on armv6 with the update applied somehow. [I'll not have powerpc access for weeks/months.] --=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-ZqVnp6gjbm>