public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tanmoy Bhattacharya <tanmoy@qcd.lanl.gov> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/3906: Internal compiler error in change_address, at emit-rtl.c:1635 Date: Wed, 07 Nov 2001 03:29:00 -0000 [thread overview] Message-ID: <20011117064602.10727.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR optimization/3906; it has been noted by GNATS. From: Tanmoy Bhattacharya <tanmoy@qcd.lanl.gov> To: rodrigc@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: optimization/3906: Internal compiler error in change_address, at emit-rtl.c:1635 Date: Mon, 13 Aug 2001 16:43:57 -0600 (MDT) In <20010813222421.24786.qmail@sourceware.cygnus.com> dated 22:24:21 -0000 August 13, 2001, rodrigc@gcc.gnu.org writes > Synopsis: Internal compiler error in change_address, at emit-rtl.c:1635 > Your example does not even compile. > With, gcc version 3.0.1 20010813 (prerelease), > I get many compilation errors, like: > > example.c:13: `p' was not declared in this scope > example.c:14: ISO C++ forbids declaration of `setlim' with no type etc. I did not claim my example was valid C++. And the command line I supplied was for invoking a C compiler, not a C++ one. Apart from the missing `line' directive after the # in the first line, it is a valid ISO standard C translaion unit, both according to C89 and C9x (which got approved last year, I do not know what it is called now). I could probably provide a C++ example, but I do not have the time to test right now. But a C compiler *must* compile every strictly conforming C program, which this one becomes if one supplies definitions for main and setloglim, possibly in a separate translation unit. Tanmoy
next reply other threads:[~2001-11-17 6:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-11-07 3:29 Tanmoy Bhattacharya [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-11-25 5:14 rodrigc 2001-11-25 4:26 rodrigc 2001-11-07 6:17 Craig Rodrigues 2001-08-13 15:24 rodrigc 2001-07-31 17:16 tanmoy
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=20011117064602.10727.qmail@sourceware.cygnus.com \ --to=tanmoy@qcd.lanl.gov \ --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).