public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Ashif S. Harji" <asharji@plg2.math.uwaterloo.ca>
To: mmitchel@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4884: g++ 3.0.2 problem with -fvolatile
Date: Tue, 26 Mar 2002 15:26:00 -0000	[thread overview]
Message-ID: <20020326232601.16940.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/4884; it has been noted by GNATS.

From: "Ashif S. Harji" <asharji@plg2.math.uwaterloo.ca>
To: mmitchel@gcc.gnu.org, <asharji@uwaterloo.ca>, <gcc-bugs@gcc.gnu.org>,
        <gcc-prs@gcc.gnu.org>, <mmitchel@gcc.gnu.org>, <pabuhr@uwaterloo.ca>,
        <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: c++/4884: g++ 3.0.2 problem with -fvolatile
Date: Tue, 26 Mar 2002 18:21:10 -0500 (EST)

 Thanks, for the prompt response.
 
 I downloaded the latest version from CVS.  Unfortunately, there is still a
 problem in the build_op_delete_call function.
 
 The compilation of the following program fails with a segault when
 -fvolatile is used but not without.  Note the addition of the constructor
 to class bar.
 
 2>@awk[114]% more test3.cc
 
 class bar {
   public :
     bar() { }
     void * operator new ( unsigned int , void * storage ) { return (void *)1;}
 };
 
 class foo {
   public:
     void mem ( ) {
         new ( 0 ) bar;
     }
 };
 
 2>@awk[115]% g++ test3.cc -c
 
 2>@awk[116]% g++ test3.cc -fvolatile -c
 test3.cc: In member function `void foo::mem()':
 test3.cc:11: internal error: Segmentation fault
 Please submit a full bug report,
 with preprocessed source if appropriate.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 
 2>@awk[117]% g++ -v
 Reading specs from ~/gccinstall/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
 Configured with: ../gcc/configure --prefix=~/gccinstall --enable-languages=c,c++ :
 Thread model: single
 gcc version 3.2 20020326 (experimental)
 
 thanks,
 ashif.
 
 On 26 Mar 2002 mmitchel@gcc.gnu.org wrote:
 
 > Synopsis: g++ 3.0.2 problem with -fvolatile
 >
 > State-Changed-From-To: analyzed->closed
 > State-Changed-By: mmitchel
 > State-Changed-When: Tue Mar 26 10:38:32 2002
 > State-Changed-Why:
 >     Fixed.
 >
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=4884
 >
 


             reply	other threads:[~2002-03-26 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-26 15:26 Ashif S. Harji [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-27 11:26 Mark Mitchell
2002-03-26 10:38 mmitchel
2002-03-25 10:53 mmitchel
2001-11-16  9:09 lerdsuwa
2001-11-08 11:36 lerdsuwa
2001-11-08 11:13 lerdsuwa
2001-11-04  2:47 asharji

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=20020326232601.16940.qmail@sources.redhat.com \
    --to=asharji@plg2.math.uwaterloo.ca \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mmitchel@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: 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).