public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert 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 16:13:00 -0000 [thread overview] Message-ID: <bug-63937-4-NPcIJ4ypJx@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 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target| |x86_64-apple-darwin14 Status|UNCONFIRMED |NEW Last reconfirmed| |2014-11-18 Component|fortran |target CC| |amylaar at gcc dot gnu.org, | |jgreenhalgh at gcc dot gnu.org Host| |x86_64-apple-darwin14 Ever confirmed|0 |1 Summary|[5 Regression] Compiling a |[5 Regression] Compiling |very simple fortran code |large arrays fails |fails. | Target Milestone|--- |5.0 Build| |x86_64-apple-darwin14 --- Comment #2 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- I can confirm, and can provide a C testcase (on x86_64-apple-darwin14 with trunk r217694): $ cat a.c void foo (void) { int v[1073741825] = {}; } $ ./bin/gcc a.c [blows up] And I know it sounds weird, but the behavior depends on the exact value of the array size, in a deterministic manner. It fails for 1073741825 (every time), but works with both 1003741825 (smaller) and 1173741825 (bigger). I stopped it at some random moments in this long "freeze", and the stable part of the backtrace is: frame #4: 0x00000001005c662a cc1`store_by_pieces_1 + 183 at expr.c:2721 frame #5: 0x00000001005c6573 cc1`store_by_pieces_1(data=0x00007fff5fbff190, align=64) + 275 frame #6: 0x00000001005d98d0 cc1`clear_storage_hints(rtx_def*, rtx_def*, block_op_methods, unsigned int, long long, unsigned long long, unsigned long long, unsigned long long) + 58 at expr.c:2605 frame #7: 0x00000001005d9896 cc1`clear_storage_hints(object=0x0000000142e44738, size=0x0000000142e46060, method=BLOCK_OP_NORMAL, expected_align=0, expected_size=-1, min_size=4294967300, max_size=4294967300, probable_max_size=4294967300) + 486 I'm not sure when that change occurred, but the only thing related to "store_by_pieces" I could find in the ChangeLog is a series of commits: 2014-11-01 James Greenhalgh <james.greenhalgh@arm.com>
next prev parent reply other threads:[~2014-11-18 16:13 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 ` fxcoudert at gcc dot gnu.org [this message] 2014-11-18 16:44 ` [Bug target/63937] [5 Regression] Compiling large arrays fails 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 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-NPcIJ4ypJx@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).