public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/34691] [4.2/4.3/4.4 Regression] Default argument checking not performed after overload resolution with C linkage
Date: Fri, 16 Jan 2009 20:03:00 -0000	[thread overview]
Message-ID: <20090116200300.30360.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34691-15588@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from jason at gcc dot gnu dot org  2009-01-16 20:03 -------
3.2.3 also fails the first testcase.  This seems to have been broken by

2001-03-01  Nathan Sidwell  <nathan@codesourcery.com>

        * decl2.c (do_nonmember_using_decl): Don't complain if we find
        same function. Do complain about ambiguating extern "C"
        declarations.

which stopped using duplicate_decls

The testcase in comment #2 (rejects-valid) passes with 3.2, but fails with 3.4.

The testcase in comment #3 (accepts-invalid) has never worked.

The first and last tests have to do with us not having a framework for checking
compatibility of extern "C" declarations; the function that complains about
incompatible declarations is duplicate_decls, and that assumes that both decls
are in the same scope and therefore we can clobber one of them.

But Dodji just added a place to check compatibility of extern "C" declarations
in his fix for 13699.  Dodji, want to extend that to handle #1 and #3?  #2
should be a separate PR I think.


-- 

jason at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dodji at gcc dot gnu dot org
      Known to fail|3.3.6                       |3.2.3 3.3.6


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34691


  parent reply	other threads:[~2009-01-16 20:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-06 20:31 [Bug c++/34691] New: Default argument checking not performed after overload resolution rideau3 at gmail dot com
2008-01-06 21:38 ` [Bug c++/34691] [4.1/4.2/4.3 Regression] Default argument checking not performed after overload resolution with C linkage rguenth at gcc dot gnu dot org
2008-01-11  8:18 ` jakub at gcc dot gnu dot org
2008-01-11 13:49 ` jakub at gcc dot gnu dot org
2008-01-11 14:12 ` jakub at gcc dot gnu dot org
2008-02-01 17:02 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:32 ` [Bug c++/34691] [4.1/4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2008-07-04 22:55 ` [Bug c++/34691] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org
2009-01-16 20:03 ` jason at gcc dot gnu dot org [this message]
2009-02-11 21:31 ` jason at gcc dot gnu dot org
2009-03-25 21:10 ` jason at gcc dot gnu dot org
2009-03-26 16:10 ` jason at gcc dot gnu dot org
2009-03-31 20:19 ` [Bug c++/34691] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-04-01  3:34 ` jason at gcc dot gnu dot org
2009-04-01 15:21 ` jason at gcc dot gnu dot org
2009-04-01 15:29 ` jason at gcc dot gnu dot org
2009-04-08  3:45 ` jason at gcc dot gnu dot org
2009-04-08  3:55 ` jason at gcc dot gnu dot org
2009-04-08  3:56 ` jason at gcc dot gnu dot org

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=20090116200300.30360.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).