public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sebastian-gcc at sipsolutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/100788] New: Internal compiler error related to #line macros(?) Date: Thu, 27 May 2021 04:22:50 +0000 [thread overview] Message-ID: <bug-100788-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788 Bug ID: 100788 Summary: Internal compiler error related to #line macros(?) Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: sebastian-gcc at sipsolutions dot net CC: marxin at gcc dot gnu.org Target Milestone: --- I first thought this might have been the identical issue as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95847 as it seemed similar. There is also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96353, but I do not think this is the same issue. We have a large file in NumPy which generates compile errors on gcc 9+ (gcc 8 seems fine as far as I can tell). The issue on NumPy is: https://github.com/numpy/numpy/issues/18529 (It is not a major issue, but I fear it might get problematic for our coverage tools when they stop using GCC 8, which I think they are still using.) I have attached the source file that generates the issue. Note that it is generated by a custom templating language, so I can't fully rule out that the inserted `#line` directives are incorrect. The one clear thing I know is that removing all `#line` directives makes the coverage compilation successfully. I expect you may need more information, but am not sure how to best provide it, considering that the file is part of the larger project. The error/log is (this one with gcc (Debian 10.2.1-6) 10.2.1 20210110, but confirmed on a gcc 11: ... x86_64-linux-gnu-gcc: numpy/core/src/common/python_xerbla.c during IPA pass: profile numpy/core/src/multiarray/einsum_sumprod.c.src: In function ‘longdouble_sum_of_products_contig_three’: numpy/core/src/multiarray/einsum_sumprod.c.src:1264:1: internal compiler error: in coverage_begin_function, at coverage.c:656 1264 | } | ^ 0x7ff60fe2cd09 __libc_start_main ../csu/libc-start.c:308 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <file:///usr/share/doc/gcc-10/README.Bugs> for instructions. error: Command "x86_64-linux-gnu-gcc -pthread --coverage -Wno-unused-result -Wsign-compare -O0 -ggdb -g -ffile-prefix-map=/build/python3.9-RNBry6/python3.9-3.9.2=. -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -Werror=vla -Werror=nonnull -Werror=pointer-arith -Wlogical-op -Werror=unused-function -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DNPY_INTERNAL_BUILD=1 -DHAVE_NPY_CONFIG_H=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -D_LARGEFILE64_SOURCE=1 -DHAVE_CBLAS -Ibuild/src.linux-x86_64-3.9/numpy/core/src/common -Ibuild/src.linux-x86_64-3.9/numpy/core/src/umath -Inumpy/core/include -Ibuild/src.linux-x86_64-3.9/numpy/core/include/numpy -Ibuild/src.linux-x86_64-3.9/numpy/distutils/include -Inumpy/core/src/common -Inumpy/core/src -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray -Inumpy/core/src/umath -Inumpy/core/src/npysort -Inumpy/core/src/_simd -I/usr/include/python3.9 -Ibuild/src.linux-x86_64-3.9/numpy/core/src/common -Ibuild/src.linux-x86_64-3.9/numpy/core/src/npymath -c build/src.linux-x86_64-3.9/numpy/core/src/multiarray/einsum_sumprod.c -o build/temp.linux-x86_64-3.9/build/src.linux-x86_64-3.9/numpy/core/src/multiarray/einsum_sumprod.o -MMD -MF build/temp.linux-x86_64-3.9/build/src.linux-x86_64-3.9/numpy/core/src/multiarray/einsum_sumprod.o.d -msse -msse2 -msse3" failed with exit status 1
next reply other threads:[~2021-05-27 4:22 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 4:22 sebastian-gcc at sipsolutions dot net [this message] 2021-05-27 4:48 ` [Bug gcov-profile/100788] " sebastian-gcc at sipsolutions dot net 2021-05-27 6:56 ` marxin at gcc dot gnu.org 2021-05-27 7:03 ` sebastian-gcc at sipsolutions dot net 2021-05-27 7:07 ` marxin at gcc dot gnu.org 2021-05-27 7:21 ` sebastian-gcc at sipsolutions dot net 2021-05-27 7:24 ` marxin at gcc dot gnu.org 2021-05-27 7:30 ` sebastian-gcc at sipsolutions dot net 2021-05-27 7:34 ` marxin at gcc dot gnu.org 2021-05-27 16:20 ` sebastian-gcc at sipsolutions dot net 2021-05-28 11:04 ` marxin at gcc dot gnu.org 2021-06-03 0:32 ` sebastian-gcc at sipsolutions dot net 2021-06-10 14:40 ` marxin at gcc dot gnu.org 2021-06-11 10:00 ` cvs-commit at gcc dot gnu.org 2021-06-11 10:01 ` marxin at gcc dot gnu.org 2021-08-13 13:50 ` cvs-commit at gcc dot gnu.org 2021-08-13 13:59 ` cvs-commit at gcc dot gnu.org 2021-08-13 14:00 ` marxin at gcc dot gnu.org 2021-12-10 20:20 ` pinskia at gcc dot gnu.org 2021-12-10 20:21 ` 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-100788-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).