public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/99489] [11 Regression] internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name() Date: Tue, 09 Mar 2021 18:00:19 +0000 [thread overview] Message-ID: <bug-99489-4-RAbuEygrh4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99489-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msebor at gcc dot gnu.org Last reconfirmed| |2021-03-09 Summary|internal compiler error: |[11 Regression] internal |during GIMPLE pass: strlen |compiler error: during |in |GIMPLE pass: strlen in |dlt_logstorage_log_file_nam |dlt_logstorage_log_file_nam |e() |e() Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords| |ice-on-valid-code --- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> --- Confirmed with a native x86_64 compiler and the full backtrace below. It's most likely a regression introduced in g:7f5ff78ff3f971c11ec67f422b2fd34281db9123. during GIMPLE pass: strlen /mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/dlt-daemon/2.18.6-r0/git/src/offlinelogstorage/dlt_offline_logstorage_behavior.c: In function ‘dlt_logstorage_log_file_name.part.0’: /mnt/b/yoe/master/build/tmp/work/cortexa72-yoe-linux-musl/dlt-daemon/2.18.6-r0/git/src/offlinelogstorage/dlt_offline_logstorage_behavior.c:54:6: internal compiler error: gimple check: expected gimple_call(error_mark), have gimple_nop() in gimple_call_fndecl, at gimple.h:3171 0xe66115 gimple_check_failed(gimple const*, char const*, int, char const*, gimple_code, tree_code) /src/gcc/master/gcc/gimple.c:1259 0xbb23bf GIMPLE_CHECK2<const gcall*> /src/gcc/master/gcc/gimple.h:74 0xb7bbe1 gimple_call_fndecl /src/gcc/master/gcc/gimple.h:3171 0xb8edf0 gimple_call_alloc_size(gimple*, generic_wide_int<wide_int_storage>*, range_query*) /src/gcc/master/gcc/builtins.c:4931 0x15cc71e handle_builtin_stxncpy_strncat /src/gcc/master/gcc/tree-ssa-strlen.c:3108 0x15caea9 handle_builtin_strncat /src/gcc/master/gcc/tree-ssa-strlen.c:2666 0x15d214f strlen_check_and_optimize_call /src/gcc/master/gcc/tree-ssa-strlen.c:5165 0x15d2d30 check_and_optimize_stmt /src/gcc/master/gcc/tree-ssa-strlen.c:5373 0x15d3917 strlen_dom_walker::before_dom_children(basic_block_def*) /src/gcc/master/gcc/tree-ssa-strlen.c:5625 0x22901c2 dom_walker::walk(basic_block_def*) /src/gcc/master/gcc/domwalk.c:309 0x15d3c0e printf_strlen_execute /src/gcc/master/gcc/tree-ssa-strlen.c:5691 0x15d3fa4 execute /src/gcc/master/gcc/tree-ssa-strlen.c:5813 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2021-03-09 18:00 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-09 16:29 [Bug tree-optimization/99489] New: " raj.khem at gmail dot com 2021-03-09 16:30 ` [Bug tree-optimization/99489] " raj.khem at gmail dot com 2021-03-09 18:00 ` msebor at gcc dot gnu.org [this message] 2021-03-09 19:29 ` [Bug tree-optimization/99489] [11 Regression] " marxin at gcc dot gnu.org 2021-03-09 19:40 ` marxin at gcc dot gnu.org 2021-03-09 19:43 ` marxin at gcc dot gnu.org 2021-03-09 19:59 ` msebor at gcc dot gnu.org 2021-03-09 22:09 ` msebor at gcc dot gnu.org 2021-03-11 18:26 ` dcb314 at hotmail dot com 2021-03-13 21:29 ` cvs-commit at gcc dot gnu.org 2021-03-13 21:30 ` msebor at gcc dot gnu.org 2021-03-13 23:39 ` raj.khem at gmail dot com
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-99489-4-RAbuEygrh4@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).