public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "familiebaumanns at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/96141] New: Coroutine and noexcept(false) destructor cause: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:2817 Date: Thu, 09 Jul 2020 21:20:19 +0000 [thread overview] Message-ID: <bug-96141-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96141 Bug ID: 96141 Summary: Coroutine and noexcept(false) destructor cause: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:2817 Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: familiebaumanns at gmail dot com Target Milestone: --- Created attachment 48853 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48853&action=edit Source file Expected Behaviour: ============== Compile without error. Actual Behaviour: ============== internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:2817 If the destructor of "Data" is changed to noexcept(true) - no compile error occurs. G++-Version: ============== g++-11 (GCC) 11.0.0 20200630 (experimental) Copyright (C) 2020 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiler Output: ============== g++-11 -fcoroutines -std=c++2a coroutine_error.cpp coroutine_error.cpp: In function ‘std::generator<int> Do()’: coroutine_error.cpp:280:1: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:2817 280 | } | ^ Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. Extended Compiler-Output: ============== g++-11 -v -save-temps -fcoroutines -std=c++2a coroutine_error.cpp bernd@bernd-pc:/mnt/c/Users/Bernd/Desktop$ g++-11 -v -save-temps -fcoroutines -std=c++2a coroutine_error.cpp Using built-in specs. COLLECT_GCC=g++-11 COLLECT_LTO_WRAPPER=/usr/local/gcc-11/libexec/gcc/x86_64-linux-gnu/11.0.0/lto-wrapper Target: x86_64-linux-gnu Configured with: ../gcc-master/configure -v --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --prefix=/usr/local/gcc-11 --enable-checking=release --enable-languages=c,c++ --disable-multilib --program-suffix=-11 Thread model: posix Supported LTO compression algorithms: zlib gcc version 11.0.0 20200630 (experimental) (GCC) COLLECT_GCC_OPTIONS='-v' '-save-temps' '-fcoroutines' '-std=c++20' '-shared-libgcc' '-mtune=generic' '-march=x86-64' '-dumpdir' 'a-' /usr/local/gcc-11/libexec/gcc/x86_64-linux-gnu/11.0.0/cc1plus -E -quiet -v -imultiarch x86_64-linux-gnu -D_GNU_SOURCE coroutine_error.cpp -mtune=generic -march=x86-64 -std=c++20 -fcoroutines -fpch-preprocess -o a-coroutine_error.ii ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu" ignoring nonexistent directory "/usr/local/gcc-11/lib/gcc/x86_64-linux-gnu/11.0.0/../../../../x86_64-linux-gnu/include" #include "..." search starts here: #include <...> search starts here: /usr/local/gcc-11/lib/gcc/x86_64-linux-gnu/11.0.0/../../../../include/c++/11.0.0 /usr/local/gcc-11/lib/gcc/x86_64-linux-gnu/11.0.0/../../../../include/c++/11.0.0/x86_64-linux-gnu /usr/local/gcc-11/lib/gcc/x86_64-linux-gnu/11.0.0/../../../../include/c++/11.0.0/backward /usr/local/gcc-11/lib/gcc/x86_64-linux-gnu/11.0.0/include /usr/local/include /usr/local/gcc-11/include /usr/local/gcc-11/lib/gcc/x86_64-linux-gnu/11.0.0/include-fixed /usr/include/x86_64-linux-gnu /usr/include End of search list. COLLECT_GCC_OPTIONS='-v' '-save-temps' '-fcoroutines' '-std=c++20' '-shared-libgcc' '-mtune=generic' '-march=x86-64' '-dumpdir' 'a-' /usr/local/gcc-11/libexec/gcc/x86_64-linux-gnu/11.0.0/cc1plus -fpreprocessed a-coroutine_error.ii -quiet -dumpdir a- -dumpbase coroutine_error.cpp -dumpbase-ext .cpp -mtune=generic -march=x86-64 -std=c++20 -version -fcoroutines -o a-coroutine_error.s GNU C++20 (GCC) version 11.0.0 20200630 (experimental) (x86_64-linux-gnu) compiled by GNU C version 11.0.0 20200630 (experimental), GMP version 6.1.0, MPFR version 3.1.4, MPC version 1.0.3, isl version isl-0.18-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 GNU C++20 (GCC) version 11.0.0 20200630 (experimental) (x86_64-linux-gnu) compiled by GNU C version 11.0.0 20200630 (experimental), GMP version 6.1.0, MPFR version 3.1.4, MPC version 1.0.3, isl version isl-0.18-GMP GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: bb9157b4f3559041919c25088e2affde coroutine_error.cpp: In function ‘std::generator<int> Do()’: coroutine_error.cpp:280:1: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:2817 280 | } | ^ Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions.
next reply other threads:[~2020-07-09 21:20 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-09 21:20 familiebaumanns at gmail dot com [this message] 2020-07-09 21:26 ` [Bug c++/96141] " familiebaumanns at gmail dot com 2020-07-09 21:28 ` familiebaumanns at gmail dot com 2020-07-12 9:30 ` [Bug c++/96141] ICE in gimplify: " familiebaumanns at gmail dot com 2021-07-18 23:48 ` pinskia 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-96141-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).