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 target/63937] [5 Regression] Compiling large arrays fails Date: Tue, 18 Nov 2014 17:10:00 -0000 [thread overview] Message-ID: <bug-63937-4-4dsHVTzhqL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63937-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63937 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> --- /* PR target/63937 */ /* { dg-do compile { target lp64 } } */ /* { dg-options "-O2" } */ void foo (char *p) { p = __builtin_assume_aligned (p, 64); __builtin_memset (p, 0, 0x100000001ULL); } might be better testcase for the testsuite (or, also use one or both the other ones, but guard them with { i?86-* x86_64-* } && lp64, not sure if all 64-bit targets support huge frames. As for the fix, the right fix agreed on IRC is replace unsigned int type for sizes with unsigned HOST_WIDE_INT in the target hook.
next prev parent reply other threads:[~2014-11-18 17:10 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-18 15:42 [Bug fortran/63937] New: [5 Regression] Compiling a very simple fortran code fails dominiq at lps dot ens.fr 2014-11-18 15:53 ` [Bug fortran/63937] " dominiq at lps dot ens.fr 2014-11-18 16:13 ` [Bug target/63937] [5 Regression] Compiling large arrays fails fxcoudert at gcc dot gnu.org 2014-11-18 16:44 ` iains at gcc dot gnu.org 2014-11-18 16:54 ` jakub at gcc dot gnu.org 2014-11-18 17:03 ` jgreenhalgh at gcc dot gnu.org 2014-11-18 17:10 ` jakub at gcc dot gnu.org [this message] 2014-11-18 22:46 ` jgreenhalgh at gcc dot gnu.org 2014-11-18 22:46 ` jgreenhalgh at gcc dot gnu.org 2014-12-04 18:19 ` yroux 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-63937-4-4dsHVTzhqL@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).