public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "herrtimson at yahoo dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106466] ICE in In function 'bool jxl_skcms_Parse(const void*, size_t, skcms_ICCProfile*)': at skcms/skcms.cc:1004:6 internal compiler error: Segmentation fault Date: Fri, 29 Jul 2022 13:19:57 +0000 [thread overview] Message-ID: <bug-106466-4-uDAy5vzwbI@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106466-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106466 --- Comment #6 from tt_1 <herrtimson at yahoo dot de> --- works with: gcc-10.3.0 gcc-10.3.1_p20211126 gcc-11.3.0 does not work with: gcc-10.4.0 the segfault is sort of spurious, its an about 1/5 to 1/7 chance for me. Is that something you can work with? and indeed these are two seperate segfaults, I got the -O1 from comment #4 now reproduced with -O2 as well
next prev parent reply other threads:[~2022-07-29 13:19 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-28 15:47 [Bug c++/106466] New: " herrtimson at yahoo dot de 2022-07-28 15:48 ` [Bug c++/106466] " herrtimson at yahoo dot de 2022-07-28 16:19 ` herrtimson at yahoo dot de 2022-07-28 16:25 ` [Bug middle-end/106466] " pinskia at gcc dot gnu.org 2022-07-28 16:30 ` [Bug c++/106466] " herrtimson at yahoo dot de 2022-07-29 7:29 ` rguenth at gcc dot gnu.org 2022-07-29 13:19 ` herrtimson at yahoo dot de [this message] 2022-08-01 8:52 ` marxin at gcc dot gnu.org 2022-08-01 8:53 ` marxin at gcc dot gnu.org 2022-08-01 13:35 ` herrtimson at yahoo dot de 2022-08-02 19:48 ` herrtimson at yahoo dot de 2022-08-02 19:51 ` herrtimson at yahoo dot de 2022-08-02 21:00 ` [Bug middle-end/106466] " herrtimson at yahoo dot de 2022-08-02 21:01 ` herrtimson at yahoo dot de 2022-08-02 21:02 ` 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-106466-4-uDAy5vzwbI@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).