public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap Date: Mon, 19 May 2003 01:26:00 -0000 [thread overview] Message-ID: <20030519012601.4191.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/9631; it has been noted by GNATS. From: Randolph Chung <randolph@tausq.org> To: Giovanni Bajo <giovannibajo@libero.it> Cc: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, Dara Hazeghi <dhazeghi@yahoo.com> Subject: Re: bootstrap/9631: [hppa64-unknown-linux-gnu] [gcc-3.2.2] fails to bootstrap Date: Sun, 18 May 2003 18:27:00 -0700 > Ok. Would you please send us a preprocessed source reproducing the bug oh, actually here's a very simple test case: tausq@gsyprf11:~/build/build-3.3/gcc$ cat bug.c struct SjLj_Function_Context { unsigned data[4]; }; tausq@gsyprf11:~/build/build-3.3/gcc$ ./xgcc -v Using built-in specs. Configured with: ../gcc-3.3/configure --enable-languages=c --prefix=/opt/palinux --disable-shared --disable-nls --with-system-zlib --without-included-gettext --enable-debug --host=hppa-linux --build=hppa-linux --target=hppa64-linux --enable-sjlj-exceptions --disable-threads Thread model: single gcc version 3.3 tausq@gsyprf11:~/build/build-3.3/gcc$ ./xgcc -B. -c bug.c bug.c:1: error: size of array `data' is too large fwiw i see that this message is printed by two places in grokdeclarator()... adding a printf i see that it's dying in the one at line 4070. randolph -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/
next reply other threads:[~2003-05-19 1:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-19 1:26 Randolph Chung [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-21 9:14 ehrhardt 2003-05-19 0:06 Giovanni Bajo 2003-05-17 17:06 Randolph Chung 2003-05-17 6:58 giovannibajo 2003-05-17 1:46 Dara Hazeghi
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=20030519012601.4191.qmail@sources.redhat.com \ --to=randolph@tausq.org \ --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).