public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "matt at godbolt dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102067] SEGFAULT in varpool_node::get_constructor during lto1 when optimising or not using debug symbols Date: Thu, 26 Aug 2021 13:31:54 +0000 [thread overview] Message-ID: <bug-102067-4-yumlV3zFqk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102067-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102067 --- Comment #13 from Matt Godbolt <matt at godbolt dot org> --- Both attached. When they're built they're built with: ``` /home/mgodbolt/dev/wave/cmake-build-release/env/bin/x86_64-conda_cos6-linux-gnu-g++ -DSPDLOG_FMT_EXTERNAL -Igenerated -I../src -I../src/wave/common/../.. -Isrc/wave -I../src/wave/.. -isystem env/include -O3 -DNDEBUG -flto -fno-fat-lto-objects -include /home/mgodbolt/dev/wave/cmake-build-release/conda_env.hpp -fconcepts -Wall -Wextra -Werror -g -fPIC -fvisibility-inlines-hidden -march=skylake -Wconversion -Wsign-conversion -Wnon-virtual-dtor -Wold-style-cast -Wpedantic -Wuseless-cast -Wdouble-promotion -Wcast-align -Wduplicated-cond -Wlogical-op -Wrestrict -Wnull-dereference -pedantic -std=gnu++17 -MD -MT src/wave/common/CMakeFiles/wave_common.dir/App.cpp.o -MF src/wave/common/CMakeFiles/wave_common.dir/App.cpp.o.d -o src/wave/common/CMakeFiles/wave_common.dir/App.cpp.o -c ../src/wave/common/App.cpp ``` The attachments were created by putting -E at the end of the line, changing the `-o` location, then gzipping the output.
next prev parent reply other threads:[~2021-08-26 13:31 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-25 14:58 [Bug c++/102067] New: " matt at godbolt dot org 2021-08-25 15:11 ` [Bug c++/102067] " marxin at gcc dot gnu.org 2021-08-25 15:24 ` matt at godbolt dot org 2021-08-25 15:39 ` marxin at gcc dot gnu.org 2021-08-25 15:40 ` matt at godbolt dot org 2021-08-25 15:41 ` matt at godbolt dot org 2021-08-25 15:47 ` marxin at gcc dot gnu.org 2021-08-25 15:50 ` marxin at gcc dot gnu.org 2021-08-25 16:02 ` matz at gcc dot gnu.org 2021-08-26 9:01 ` marxin at gcc dot gnu.org 2021-08-26 13:25 ` matt at godbolt dot org 2021-08-26 13:30 ` matt at godbolt dot org 2021-08-26 13:30 ` matt at godbolt dot org 2021-08-26 13:31 ` matt at godbolt dot org [this message] 2021-08-26 14:16 ` marxin at gcc dot gnu.org 2021-08-26 15:23 ` matt at godbolt dot org 2021-08-26 17:53 ` marxin at gcc dot gnu.org 2021-08-26 18:47 ` matt at godbolt dot org 2021-08-26 18:59 ` [Bug ipa/102067] " pinskia at gcc dot gnu.org 2021-08-27 7:27 ` marxin at gcc dot gnu.org 2021-08-27 7:28 ` marxin at gcc dot gnu.org 2021-08-27 12:22 ` matt at godbolt dot org 2022-11-10 20:28 ` samuelpmish at gmail dot com 2022-11-11 12:48 ` marxin at gcc dot gnu.org 2022-11-11 15:42 ` samuelpmish at gmail dot com 2022-11-14 9:53 ` marxin 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-102067-4-yumlV3zFqk@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).