public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Steve Madsen <steve@h2eye.com>
To: egcs-bugs@egcs.cygnus.com
Subject: Re: BUG REPORT: internal compiler error
Date: Sun, 31 Oct 1999 23:03:00 -0000	[thread overview]
Message-ID: <3.0.6.32.19991008121335.007a1ec0@h2eye.com> (raw)

Hello there,

I just got a message that I should send a bug report.  I'm
running linux (Redhat 5.2), kernel 2.2.9 on i386 (AMD K6),
gcc version:

2.7.2.3  (Output of gcc -v)
gcc version egcs-2.90.29 980515 (egcs-1.0.3 release)  (Output of g++ -v)

Used command line:
   g++ test1.cc -o test1   
to compile.

The only difference between the two examples is that one
uses "dumm" as a placeholder and one "dum".  It appears
that at least a four character string is necessary or things won't
work.

The following code compiles and runs:


#include <iostream>

int main()
{

  char *myStr = "thisStringIsSeveralCharsLong";

  int  myStrLen = strlen( myStr ) + 1;
  
  char testCharArr[][ myStrLen ]    = { "dumm", "otherstring", "yetanother" };

  strcpy ( testCharArr[0], myStr );

  cout << "testCharArr[0] = " << testCharArr[0] << "\n";
 
}



The following code results in an error:

#include <iostream>

int main()
{

  char *myStr = "thisStringIsSeveralCharsLong";

  int  myStrLen = strlen( myStr ) + 1;
  
  char testCharArr[][ myStrLen ]    = { "dum", "otherstring", "yetanother" };

  strcpy ( testCharArr[0], myStr );

  cout << "testCharArr[0] = " << testCharArr[0] << "\n";
 
}


-- 
Steve Madsen, Computer Graphics Department
H2 Eye, Ltd.
24-28 Hatton Wall
London  EC1N 8JH
United Kingdom
Tel:   +44 (0) 171 404 9600
Fax:   +44 (0) 171 404 9490
Email: steve@h2eye.com



             reply	other threads:[~1999-10-31 23:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-31 23:03 Steve Madsen [this message]
1999-10-08  4:23 ` Gerald Pfeifer
  -- strict thread matches above, loose matches on Subject: below --
2006-11-03 15:05 BUG report : Internal " R.J.Sivakumar
2001-06-13 19:05 bug report: " Rob Kaper
2000-09-14  1:16 BUG REPORT: Internal Compiler error Thomas Hendel
     [not found] <Pine.HPX.4.21.0004272125500.1168-101000@verdande.diku.dk>
2000-04-27 13:33 ` bug report: Internal compiler error Martin v. Loewis
1999-06-17 11:09 Bug Report: Internal Compiler Error Bill Wendling
1999-06-30 23:07 ` Martin v. Loewis
1999-05-31 21:06 Bug report: internal compiler error Sascha Schumann
1998-08-22  1:58 Bug Report: Internal Compiler Error Ramon Fernandez
1998-08-22  8:54 ` Martin von Loewis
1998-07-10  5:31 Bug report: internal compiler error C. van Reeuwijk
1998-07-11  7:27 ` Martin von Loewis

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=3.0.6.32.19991008121335.007a1ec0@h2eye.com \
    --to=steve@h2eye.com \
    --cc=egcs-bugs@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).