public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: dsittig@ambit.com (Daniel Sittig)
To: egcs-bugs@cygnus.com
Subject: compiler error ?
Date: Thu, 15 Oct 1998 17:47:00 -0000 [thread overview]
Message-ID: <199810160043.RAA05411@bart.ambit.com> (raw)
Hello,
I potentially found a bug in the egcs1.1b release
- egcs -v :
gcc version egcs-2.91.57 19980901 (egcs-1.1 release)
The file is attached both in plain C++ syntax and in .ii format,
options were not specified.
Regards,
--
Daniel Sittig AMBIT Design Systems
A subsidary of Cadence Design Systems
2500 Augustine Drive
email dsittig@ambit.com Santa Clara, CA 95054
tel 408 566 8141
web http://www.ambit.com
>From wferi@bolyai1.elte.hu Thu Oct 15 22:54:00 1998
From: Ferenc Wagner <wferi@bolyai1.elte.hu>
To: egcs-bugs@cygnus.com
Subject: g++ bug report
Date: Thu, 15 Oct 1998 22:54:00 -0000
Message-id: <Pine.LNX.3.96.981016050814.4675A-200000@bolyai1.elte.hu>
X-SW-Source: 1998-10/msg00489.html
Content-length: 775
Hi,
I got the following message from the compiler:
sep.cc:19: warning: ANSI C++ forbids initialization of member `separation'
sep.cc:19: Internal compiler error.
sep.cc:19: Please submit a full bug report to `egcs-bugs@cygnus.com'.
So here it is. Find the related sources attached.
Output from `g++ -v':
Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.90.27/specs
gcc version egcs-2.90.27 980315 (egcs-1.0.2 release)
The offending command was: `g++ sep.cpp'
The operating system is RedHat Linux 5.1, default gcc configuration. No
modifications have been made to the gcc sources.
I agree the code is somehow foolish; anyway, I was said it was a bug...
Anyway, it appeared when I introduced the `separation' object.
Hope it helps, cheers: Ferenc.
next reply other threads:[~1998-10-15 17:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-15 17:47 Daniel Sittig [this message]
1998-12-03 14:57 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
1998-08-20 8:15 compiler error? Jens Thiele
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=199810160043.RAA05411@bart.ambit.com \
--to=dsittig@ambit.com \
--cc=egcs-bugs@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).