public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/95362] [11 regression] pr34457-1.c and pr92088-1.c fail on arm and aarch64 since g:a746f952abb78af9db28a7f3bce442e113877c9c
Date: Wed, 27 May 2020 12:52:29 +0000	[thread overview]
Message-ID: <bug-95362-4-Tne5JrCUXd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95362-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|arm aarch64                 |arm, aarch64, x86_64

--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
One can reproduce that on x86_64-linux-gnu as well:

$ cat ice.c
void bar();

int
main(int argc, char **argv) {
  struct s {
    char b[argc];
  };

  void nested(struct s x) {}
  bar(nested);

  return 0;
}

$ gcc -O2 -flto ice.c
during IPA pass: cp
lto1: internal compiler error: in operator[], at vec.h:867
0x665956 vec<ipa_jump_func, va_gc, vl_embed>::operator[](unsigned int)
        /home/marxin/Programming/gcc/gcc/vec.h:867
0x665956 ipa_get_ith_jump_func
        /home/marxin/Programming/gcc/gcc/ipa-prop.h:825
0x667e38 vec<lto_encoder_entry, va_heap, vl_ptr>::operator[](unsigned int)
        /home/marxin/Programming/gcc/gcc/alloc-pool.h:260
0x667e38 lto_symtab_encoder_deref
        /home/marxin/Programming/gcc/gcc/lto-streamer.h:1173
0x667e38 ipa_prop_read_section
        /home/marxin/Programming/gcc/gcc/ipa-prop.c:5059
0x667e38 ipa_prop_read_jump_functions()
        /home/marxin/Programming/gcc/gcc/ipa-prop.c:5089
0xc5299e ipa_read_summaries_1
        /home/marxin/Programming/gcc/gcc/passes.c:2837
0x850cec read_cgraph_and_symbols(unsigned int, char const**)
        /home/marxin/Programming/gcc/gcc/lto/lto-common.c:2921
0x837a52 lto_main()
        /home/marxin/Programming/gcc/gcc/lto/lto.c:625
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.
lto-wrapper: fatal error: gcc returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status

  parent reply	other threads:[~2020-05-27 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 11:32 [Bug other/95362] New: [11 regression] pr34457-1.c fails on arm since ga746f952abb78af9db28a7f3bce442e113877c9c clyon at gcc dot gnu.org
2020-05-27 11:34 ` [Bug other/95362] [11 regression] pr34457-1.c and pr92088-1.c fail on arm and aarch64 " clyon at gcc dot gnu.org
2020-05-27 11:43 ` [Bug lto/95362] [11 regression] pr34457-1.c and pr92088-1.c fail on arm and aarch64 since g:a746f952abb78af9db28a7f3bce442e113877c9c marxin at gcc dot gnu.org
2020-05-27 12:52 ` marxin at gcc dot gnu.org [this message]
2020-05-28  7:32 ` rguenth at gcc dot gnu.org
2020-05-29 10:26 ` cvs-commit at gcc dot gnu.org
2020-08-14 11:37 ` cvs-commit at gcc dot gnu.org
2020-10-16 11:47 ` rguenth at gcc dot gnu.org
2020-10-16 11:47 ` rguenth 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-95362-4-Tne5JrCUXd@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).