public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/8730: [3.2/3.3/3.4 regression] Cannot compile C function inside other C function Date: Tue, 01 Apr 2003 18:26:00 -0000 [thread overview] Message-ID: <20030401182601.10662.qmail@sources.redhat.com> (raw) The following reply was made to PR c/8730; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: Steven Bosscher <s.bosscher@student.tudelft.nl> Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, ilgis@num.uni-sb.de, gcc-prs@gcc.gnu.org, info@ilghiz.com, mark@codesourcery.com Subject: Re: c/8730: [3.2/3.3/3.4 regression] Cannot compile C function inside other C function Date: Tue, 1 Apr 2003 10:22:29 -0800 On Tue, Apr 01, 2003 at 11:08:39AM +0200, Steven Bosscher wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8730 > > I cannot reproduce this PR anymore. The testcase, > > void foo() > { > void* bar(int i, int A[1][i]) { return A[0]; } > } > > compilers fine for me with today's CVS (3.3 20030401). Could it be > that this PR got fixed with Mark Mitchell's patch for 9936? > (http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00018.html) My regression hunting scripts verify that this patch fixes the problem. I used the original larger test case on i686-pc-linux-gnu. Janis
next reply other threads:[~2003-04-01 18:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-01 18:26 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-01 17:57 mmitchel 2003-04-01 9:16 Steven Bosscher
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=20030401182601.10662.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --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).