public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/96597] valgrind error in do_hoist_insertion during O3 build Date: Thu, 13 Aug 2020 08:25:11 +0000 [thread overview] Message-ID: <bug-96597-4-yqOdjfl4WQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96597-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96597 --- Comment #2 from David Binderman <dcb314 at hotmail dot com> --- Created attachment 49055 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49055&action=edit gzipped C source code This attached file is preprocessed from libgcc/libgcov-driver.c. This line is required to compile it: /home/dcb/gcc/working/./gcc/xgcc -B/home/dcb/gcc/working/./gcc/ -B/home/dcb/gcc/results.20200812.valgrind/x86_64-pc-linux-gnu/bin/ -B/home/dcb/gcc/results.20200812.valgrind/x86_64-pc-linux-gnu/lib/ -isystem /home/dcb/gcc/results.20200812.valgrind/x86_64-pc-linux-gnu/include -isystem /home/dcb/gcc/results.20200812.valgrind/x86_64-pc-linux-gnu/sys-include -g -O3 -O2 -g -O3 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag -Wstrict-prototypes -Wmissing-prototypes -Wno-error=format-diag -Wold-style-definition -isystem ./include -fpic -mlong-double-80 -DUSE_ELF_SYMVER -fcf-protection -mshstk -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -fpic -mlong-double-80 -DUSE_ELF_SYMVER -fcf-protection -mshstk -I. -I. -I../.././gcc -I../../../trunk.git/libgcc -I../../../trunk.git/libgcc/. -I../../../trunk.git/libgcc/../gcc -I../../../trunk.git/libgcc/../include -I../../../trunk.git/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -MT _gcov.o -MD -MP -MF _gcov.dep -DL_gcov -c
next prev parent reply other threads:[~2020-08-13 8:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-13 7:18 [Bug c/96597] New: " dcb314 at hotmail dot com 2020-08-13 7:47 ` [Bug c/96597] " marxin at gcc dot gnu.org 2020-08-13 8:25 ` dcb314 at hotmail dot com [this message] 2020-08-13 8:40 ` dcb314 at hotmail dot com 2020-08-13 8:43 ` dcb314 at hotmail dot com 2020-08-13 9:00 ` marxin at gcc dot gnu.org 2020-08-13 10:34 ` dcb314 at hotmail dot com 2020-08-13 10:36 ` marxin at gcc dot gnu.org 2020-08-13 11:02 ` marxin at gcc dot gnu.org 2020-08-17 12:34 ` [Bug tree-optimization/96597] " marxin at gcc dot gnu.org 2020-08-24 7:30 ` cvs-commit at gcc dot gnu.org 2020-08-24 7:36 ` marxin at gcc dot gnu.org 2020-09-01 9:26 ` cvs-commit at gcc dot gnu.org 2021-05-18 7:05 ` cvs-commit 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-96597-4-yqOdjfl4WQ@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).