public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "enolan at alumni dot cmu.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107255] New: ation and definition of a template function which vary in use of concept auto syntax are interpreted as ambiguous overloadsdeclar
Date: Fri, 14 Oct 2022 01:40:39 +0000	[thread overview]
Message-ID: <bug-107255-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107255

            Bug ID: 107255
           Summary: ation and definition of a template function which vary
                    in use of concept auto syntax are interpreted as
                    ambiguous overloadsdeclar
           Product: gcc
           Version: 12.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: enolan at alumni dot cmu.edu
  Target Milestone: ---

This is a rejects-valid bug where GCC has trouble determining that a
declaration and definition which vary only in their use of concept auto syntax
are for the same function and not multiple ambiguous overloads.

Compiler explorer link: https://godbolt.org/z/4Tjcz49d9

Minimal reproduction:

template <typename T>
concept Foo = true;

void bar(Foo auto);

template <Foo F>
void bar(F) {}

void baz() {
    bar(0);
}

> the exact version of GCC

gcc version 12.2.1 20220819 (Red Hat 12.2.1-2) (GCC)

> the system type

Fedora release 38 (Rawhide)

> the options given when GCC was configured/built

Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,d,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --enable-libstdcxx-backtrace
--with-linker-hash-style=gnu --enable-plugin --enable-initfini-array
--with-isl=/builddir/build/BUILD/gcc-12.2.1-20220819/obj-x86_64-redhat-linux/isl-install
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-offload-defaulted --enable-gnu-indirect-function --enable-cet
--with-tune=generic --with-arch_32=i686 --build=x86_64-redhat-linux
--with-build-config=bootstrap-lto --enable-link-serialization=1

> the complete command line that triggers the bug

g++ -std=c++20 poc.cpp

> the compiler output

poc.cpp: In function ‘void baz()’:
poc.cpp:10:8: error: call of overloaded ‘bar(int)’ is ambiguous
   10 |     bar(0);
      |     ~~~^~~
poc.cpp:4:6: note: candidate: ‘void bar(auto:1) [with auto:1 = int]’
    4 | void bar(Foo auto);
      |      ^~~
poc.cpp:7:6: note: candidate: ‘void bar(F) [with F = int]’
    7 | void bar(F) {}
      |      ^~~

             reply	other threads:[~2022-10-14  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-14  1:40 enolan at alumni dot cmu.edu [this message]
2022-10-15  7:00 ` [Bug c++/107255] declaration and definition of a template function which vary in use of concept auto syntax are interpreted as ambiguous overloads de34 at live dot cn
2022-10-15 13:33 ` redi at gcc dot gnu.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=bug-107255-4@http.gcc.gnu.org/bugzilla/ \
    --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).