public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: lerdsuwa@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	john_maddock@compuserve.com, lerdsuwa@gcc.gnu.org,
	nathan@gcc.gnu.org
Subject: Re: c++/8503: [3.2 regression] strange behaviour of function types
Date: Thu, 05 Dec 2002 06:26:00 -0000	[thread overview]
Message-ID: <20021205142620.16845.qmail@sources.redhat.com> (raw)

Synopsis: [3.2 regression] strange behaviour of function types

Responsible-Changed-From-To: lerdsuwa->nathan
Responsible-Changed-By: lerdsuwa
Responsible-Changed-When: Thu Dec  5 06:26:19 2002
Responsible-Changed-Why:
    Hi Nathan,
    
    Awhile back you fixed a bug related to DR 295 implementation
    on the main trunk with relevant ChangeLog entry below:
    
      2002-09-16  Nathan Sidwell  <nathan@codesourcery.com>
    
            Remove DR 295 implementation.
            * pt.c (check_cv_quals_for_unify): Disable function & method cases.
            * tree.c (cp_build_qualified_type_real): Likewise. Don't warn
            about ignoring volatile qualifiers.
    
    However the bug is still present in the 3.2 branch
    and there are two GNATS report about the problem: PR8503
    and PR7774.  I've verified that the patch fixes these
    bugs.  Would you consider applying it for the 3.2 branch
    as well?
    
    --Kriang

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8503


             reply	other threads:[~2002-12-05 14:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-05  6:26 lerdsuwa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-26  4:56 nathan
2002-12-03  6:35 lerdsuwa

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=20021205142620.16845.qmail@sources.redhat.com \
    --to=lerdsuwa@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=john_maddock@compuserve.com \
    --cc=nathan@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).