public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: jason@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6331: g++ 3.1 looses const qualifiers
Date: Wed, 24 Apr 2002 10:26:00 -0000	[thread overview]
Message-ID: <20020424172601.6628.qmail@sources.redhat.com> (raw)

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

From: Mark Mitchell <mark@codesourcery.com>
To: Jason Merrill <jason@redhat.com>
Cc: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>,
   "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/6331: g++ 3.1 looses const qualifiers
Date: Wed, 24 Apr 2002 10:21:16 -0700

 > The original bug report that the testcase is derived from complained about
 > the error; the customer said that either the extension should be dropped
 > or the testcase should be accepted.  Neither of those came to pass.
 >
 > I wouldn't object to making the pedwarn unconditional.
 
 I agree; let's just kill this extension -- it is totally undocumented,
 and provides no real power since memcpy/loops do the same thing.
 
 Do you have time to make that change, or do you want me to do it?
 
 Thanks,
 
 --
 Mark Mitchell                   mark@codesourcery.com
 CodeSourcery, LLC               http://www.codesourcery.com
 


             reply	other threads:[~2002-04-24 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 10:26 Mark Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-25  1:27 jason
2002-04-24 10:36 Mark Mitchell
2002-04-24 10:36 Jason Merrill
2002-04-24 10:26 Jason Merrill
2002-04-24  9:06 Mark Mitchell
2002-04-24  2:05 jason
2002-04-23 15:24 schwab
2002-04-23  1:43 mmitchel
2002-04-22 11:14 mmitchel
2002-04-17  2:46 pthomas

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=20020424172601.6628.qmail@sources.redhat.com \
    --to=mark@codesourcery.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jason@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).