public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Luben Tuikov <ltuikov@yahoo.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/3101: ICE -- seg. fault compiling and encountering C::Angle(...) Date: Sat, 09 Jun 2001 22:16:00 -0000 [thread overview] Message-ID: <20010610051601.3575.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/3101; it has been noted by GNATS. From: Luben Tuikov <ltuikov@yahoo.com> To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/3101: ICE -- seg. fault compiling and encountering C::Angle(...) Date: Sat, 9 Jun 2001 22:11:26 -0700 (PDT) Ok, I figured it out: If a class' constructor uses default values for the parameters and then only few are set in an object definition -- then the compiler seg. faults! E.g: class A { public: A(int a=0, int b=0, int c=1) { ... } ... } class B { public: SomeMethod(A v = A(0,0)); } Oops -- seg fault at line containing SomeMethod(...)! This is the problem with c++/3101... Will this be fixed...? or already has been? Luben --- gcc-gnats@gcc.gnu.org wrote: > Thank you very much for your problem report. > It has the internal identification `c++/3101'. > The individual assigned to look at your > report is: unassigned. > > >Category: c++ > >Responsible: unassigned > >Synopsis: ICE -- seg. fault compiling and > encountering C::Angle(...) > >Arrival-Date: Sat Jun 09 15:36:00 PDT 2001 __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/
next reply other threads:[~2001-06-09 22:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-09 22:16 Luben Tuikov [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-14 19:21 rodrigc 2001-06-09 15:36 ltuikov
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=20010610051601.3575.qmail@sourceware.cygnus.com \ --to=ltuikov@yahoo.com \ --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).