public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/10472 Date: Tue, 29 Apr 2003 00:56:00 -0000 [thread overview] Message-ID: <20030429005600.4333.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/10472; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: Giovanni Bajo <giovannibajo@libero.it> Cc: gcc-gnats@gcc.gnu.org, <gcc-bugs@gcc.gnu.org> Subject: Re: bootstrap/10472 Date: Mon, 28 Apr 2003 19:54:55 -0500 (CDT) > about PR/10472, maybe you can give me a hand: I have attacched to this mail > the precompiled file that triggers the ICE. Can you try compiling this with > a recent 3.4 (assuming you have one available) and see if you can reproduce > the ICE? The full command line is written in the PR. Yes, this triggers it: ---------------------- void * mempcpy (void *, const void *, unsigned); static char *stpcpy (char *dest, const char *src); void foo() { stpcpy (mempcpy (stpcpy (stpcpy (0,0), 0), 0, 1), 0); } ---------------------- g/y> ~/bin/gcc-3.4-pre/bin/gcc -O0 -c dcigettext.i dcigettext.i:2: warning: `stpcpy' used but never defined g/y> ~/bin/gcc-3.4-pre/bin/gcc -O -c dcigettext.i dcigettext.i: In function `foo': dcigettext.i:6: internal compiler error: in instantiate_virtual_regs_lossage, at function.c:3782 I'll change the synopsis of the bug report shortly, to indicate that it is not a bootstrap problem, but a problem in the middle-end. W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/
reply other threads:[~2003-04-29 0:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030429005600.4333.qmail@sources.redhat.com \ --to=bangerth@ices.utexas.edu \ --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).