public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug gcov-profile/100788] Internal compiler error related to #line macros(?) Date: Thu, 27 May 2021 07:24:54 +0000 [thread overview] Message-ID: <bug-100788-4-AfyI8sErCT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100788-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788 --- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to seberg from comment #5) > > Now I miss the command line. > > Do you mean more than the failing call?: > > x86_64-linux-gnu-gcc -pthread --coverage -O0 -ggdb -g > -ffile-prefix-map=/build/python3.9-RNBry6/python3.9-3.9.2=. > -fstack-protector-strong -g -fwrapv -O2 -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 -msse2 -msse3 This works for me. Btw. you reproduce the issue when using the pre-processed source file? The crash is about a function that has wrong source start and end location from C front-end. > > (with some warning flags removed compared to the initial report; I can try > to zip up the dependencies tomorrow. To make it reproducable)
next prev parent reply other threads:[~2021-05-27 7:24 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-27 4:22 [Bug gcov-profile/100788] New: " sebastian-gcc at sipsolutions dot net 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 [this message] 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-AfyI8sErCT@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).