public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/6196: ICE in copy_to_mode_reg, at explow.c:711
Date: Tue, 13 May 2003 01:26:00 -0000	[thread overview]
Message-ID: <20030513012601.29924.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/6196; it has been noted by GNATS.

From: Dara Hazeghi <dhazeghi@yahoo.com>
To: x_clerc@yahoo.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: other/6196: ICE in copy_to_mode_reg, at explow.c:711
Date: Mon, 12 May 2003 18:18:58 -0700

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- 
 trail&database=gcc&pr=6196
 
 Hello,
 
 I cannot reproduce the problem in this report. WIth gcc 3.2, 3.3 branch  
 or mainline (20030510), I get:
 
 bash-2.04$ /usr/bin/g++ junk.cc
 In file included from /usr/include/c++/3.2/backward/iostream.h:31,
                   from junk.cc:1:
 /usr/include/c++/3.2/backward/backward_warning.h:32:2: warning:  
 #warning This file includes at least one deprecated or antiquated  
 header. Please consider using one of the 32 headers found in section  
 17.4.1.2 of the C++ standard. Examples include substituting the <X>  
 header for the <X.h> header for C++ includes, or <sstream> instead of  
 the deprecated header <strstream.h>. To disable this warning use  
 -Wno-deprecated.
 junk.cc: In function `int main()':
 junk.cc:6: pointer of type `void *' used in arithmetic
 junk.cc:6: `const void*' is not a pointer-to-object type
 
 Can the submitter please verify with a current version of gcc (ie  
 3.2.3) whether this problem is fixed? Thanks,
 
 Dara
 


             reply	other threads:[~2003-05-13  1:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13  1:26 Dara Hazeghi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13  6:51 steven
2002-04-07 18:35 rodrigc

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=20030513012601.29924.qmail@sources.redhat.com \
    --to=dhazeghi@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: 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).