public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rvmallad at amazon dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/107433] New: 510.parest_r, call of overloaded 'back_interpolate' is ambiguous Date: Thu, 27 Oct 2022 12:02:53 +0000 [thread overview] Message-ID: <bug-107433-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107433 Bug ID: 107433 Summary: 510.parest_r, call of overloaded 'back_interpolate' is ambiguous Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: rvmallad at amazon dot com Target Milestone: --- $ g++ -mabi=lp64 -c -o source/fe/fe_tools.o -DSPEC -DNDEBUG -Iinclude -I. -DSPEC_AUTO_SUPPRESS_OPENMP -g -O3 -mcpu=native -fpermissive -DSPEC_LP64 source/fe/fe_tools.cc source/fe/fe_tools.cc:1301:21: error: call of overloaded 'back_interpolate(const dealii::DoFHandler<3, 3>&, const dealii::BlockVector<double>&, const dealii::FiniteElement<3, 3>&, dealii::BlockVector<double>&)' is ambiguous 1301 | back_interpolate(dof1, u1, dof2.get_fe(), u1_interpolated); | ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ $ /home/ubuntu/gccmainline/bin/g++ -v Using built-in specs. COLLECT_GCC=/home/ubuntu/gccmainline/bin/g++ COLLECT_LTO_WRAPPER=/home/ubuntu/gccmainline/libexec/gcc/aarch64-unknown-linux-gnu/13.0.0/lto-wrapper Target: aarch64-unknown-linux-gnu Configured with: ../configure --prefix=/home/ubuntu/gccmainline --enable-languages=c,fortran Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.0 20221026 (experimental) (GCC)
next reply other threads:[~2022-10-27 12:02 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-27 12:02 rvmallad at amazon dot com [this message] 2022-10-27 14:45 ` [Bug c++/107433] " marxin at gcc dot gnu.org 2022-10-27 14:51 ` rvmallad at amazon dot com
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-107433-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: linkBe 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).