From: Joe Buck <jbuck@synopsys.com>
To: egcs@cygnus.com
Subject: glitch in gcc/invoke.texi
Date: Fri, 29 Aug 1997 05:38:34 -0000 [thread overview]
Message-ID: <199708290538.WAA24054@atrus.synopsys.com> (raw)
Don't forget to double those @ signs in texi docs.
*** invoke.texi.old 1997/08/29 05:32:34
--- invoke.texi 1997/08/29 05:34:24
***************
*** 2198,2204 ****
they have helped determine the efficacy of various
approaches to improving loop optimizations.
! Please let us (@code{egcs@cygnus.com and fortran@@gnu.ai.mit.edu})
know how use of these options affects
the performance of your production code.
We're very interested in code that runs @emph{slower}
--- 2198,2204 ----
they have helped determine the efficacy of various
approaches to improving loop optimizations.
! Please let us (@code{egcs@@cygnus.com and fortran@@gnu.ai.mit.edu})
know how use of these options affects
the performance of your production code.
We're very interested in code that runs @emph{slower}
WARNING: multiple messages have this Message-ID
From: Kriang Lerdsuwanakij <lerdsuwa@scf-fs.usc.edu>
To: egcs@cygnus.com
Subject: a g++ bug in namespace code
Date: Fri, 29 Aug 1997 06:00:07 -0000 [thread overview]
Message-ID: <199708290538.WAA24054@atrus.synopsys.com> (raw)
Message-ID: <19970829060007.lDILp5r4TFvBiqDKyNm3u2usygVIaSl6vEREc-3xsPI@z> (raw)
Hi,
I looked at namespace codes in g++ and found a bug in unnamed namespace.
The 'get_unique_name' function in 'cp/decl.c' starts replacing special
symbols with '_' at the 12th byte of the allocated buffer but the buffer
may be smaller than that. It causes internal compiler error in my
system. The following patch fixs the bug.
Kriang
* decl.c (get_unique_name): Prevent reading/writing outside the
unique string when replacing chars to `_'.
--- decl.c.orig Thu Aug 28 20:17:36 1997
+++ decl.c Thu Aug 28 20:18:04 1997
@@ -1694,7 +1694,7 @@
/* Don't need to pull weird characters out of global names. */
if (p != first_global_object_name)
{
- for (p = buf+11; *p; p++)
+ for (p = buf+2; *p; p++)
if (! ((*p >= '0' && *p <= '9')
#ifndef NO_DOLLAR_IN_LABEL /* this for `$'; unlikely, but... -- kr */
|| *p == '$'
next reply other threads:[~1997-08-29 5:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-29 5:38 Joe Buck [this message]
1997-08-29 6:00 ` a g++ bug in namespace code Kriang Lerdsuwanakij
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=199708290538.WAA24054@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
/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: link
Be 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).