public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9516: [2003-02-01] Internal error when using a big array Date: Fri, 04 Apr 2003 17:56:00 -0000 [thread overview] Message-ID: <20030404175601.4932.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9516; it has been noted by GNATS. From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de> To: gcc-gnats@gcc.gnu.org, p.allix@ifrance.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org Cc: Subject: Re: c/9516: [2003-02-01] Internal error when using a big array Date: Fri, 4 Apr 2003 19:48:41 +0200 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9516 Hi, this PR is about a segfault when initializing an array like this: unsigned char tab[] = { 1,2,3,4,<several million initializer element> }; The reason is a stack overflow because the initializer elements are in a TREE_LIST and this list is passed to expr.c:safe_from_p which does an infinite recursion in this piece of code: case 'x': if (TREE_CODE (exp) == TREE_LIST) return ((TREE_VALUE (exp) == 0 || safe_from_p (x, TREE_VALUE (exp), 0)) && (TREE_CHAIN (exp) == 0 || safe_from_p (x, TREE_CHAIN (exp), 0))); I guess that rewriting this as: case 'x': if (TREE_CODE (exp) == TREE_LIST) { tree tmp; for (tmp = exp; tmp; tmp = TREE_CHAIN(tmp)) { if (TREE_VALUE(exp) != 0 && !safe_from_p (x, TREE_VALUE (tmp), 0)) return 0; } return 1; } should fix this PR. I'll bootstrap and regtest. regards Christian -- THAT'S ALL FOLKS!
next reply other threads:[~2003-04-04 17:56 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-04 17:56 Christian Ehrhardt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-09 4:48 rth 2003-02-01 22:14 bangerth
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=20030404175601.4932.qmail@sources.redhat.com \ --to=ehrhardt@mathematik.uni-ulm.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).