public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mjs@ams.org To: gcc-gnats@gcc.gnu.org Subject: c/3127: gcc-2.95.3 has very slight error in gcc/function.c Date: Mon, 11 Jun 2001 13:46:00 -0000 [thread overview] Message-ID: <20010611203653.5406.qmail@sourceware.cygnus.com> (raw) >Number: 3127 >Category: c >Synopsis: gcc-2.95.3 has very slight error in gcc/function.c >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Jun 11 13:46:02 PDT 2001 >Closed-Date: >Last-Modified: >Originator: mjs@ams.org >Release: gcc-2.95.3 >Organization: >Environment: SunOS 5.8 Generic_108528-02 sun4u sparc SUNW,Ultra-60 ucbcc: Sun WorkShop 6 update 1 C 5.2 2000/09/11 >Description: When attempting to run a make on the source for gcc-2.95.3 on the above system type, it fails when trying to make function.o out of gcc/function.c complaining of a missing #endif at EOF. Not really a bug, just not something I would want in a distro... >How-To-Repeat: just run a make >Fix: here are the original last two lines of function.c: #endif /* HAVE_prologue or HAVE_epilogue */ } and here is what should be there: #endif /* HAVE_prologue or HAVE_epilogue */ #endif } >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-06-11 13:46 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=20010611203653.5406.qmail@sourceware.cygnus.com \ --to=mjs@ams.org \ --cc=gcc-gnats@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).