public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/99489] New: internal compiler error: during GIMPLE pass: strlen in dlt_logstorage_log_file_name()
Date: Tue, 09 Mar 2021 16:29:57 +0000	[thread overview]
Message-ID: <bug-99489-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99489

            Bug ID: 99489
           Summary: internal compiler error: during GIMPLE pass: strlen in
                    dlt_logstorage_log_file_name()
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: raj.khem at gmail dot com
  Target Milestone: ---

Created attachment 50339
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50339&action=edit
testcase

Attached test is causing ICE on aarch64 targets


aarch64-yoe-linux-musl-gcc -O2 -c dlt_offline_logstorage_behavior.i
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: Segmentation fault
   54 | void dlt_logstorage_log_file_name(char *log_file_name,
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
0x1669eb8 internal_error(char const*, ...)
        ???:0
0x679c22 private_lookup_attribute(char const*, unsigned long, tree_node*)
        ???:0
0x77a73f gimple_call_alloc_size(gimple*, generic_wide_int<wide_int_storage>*,
range_query*)
        ???:0
0xd65005 strlen_dom_walker::before_dom_children(basic_block_def*)
        ???:0
0x14e02f7 dom_walker::walk(basic_block_def*)
        ???:0

             reply	other threads:[~2021-03-09 16:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-09 16:29 raj.khem at gmail dot com [this message]
2021-03-09 16:30 ` [Bug tree-optimization/99489] " raj.khem at gmail dot com
2021-03-09 18:00 ` [Bug tree-optimization/99489] [11 Regression] " msebor at gcc dot gnu.org
2021-03-09 19:29 ` 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@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: link
Be 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).