public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "erick.ochoa@theobroma-systems.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/95336] New: Bad code gen omnetpp_r aarch64
Date: Tue, 26 May 2020 14:49:36 +0000	[thread overview]
Message-ID: <bug-95336-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 95336
           Summary: Bad code gen omnetpp_r aarch64
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ipa
          Assignee: unassigned at gcc dot gnu.org
          Reporter: erick.ochoa@theobroma-systems.com
                CC: marxin at gcc dot gnu.org
  Target Milestone: ---

Hello,

I have been using a configuration file to compile and run CPU2017. This
configuration file worked well with gcc9, but it doesn't seem to work well with
gcc10. I am aware of the instructions outlined in "Porting to GCC 10" [0] and I
believe I have followed them. However, at least for omnetpp_r there still
seemed to be an issue. Compilation succeeded, gave several warnings (including
the following):

simulator/matchexpression.tab.cc: In function
'matchexpressionyyparse.constprop.isra':
simulator/matchexpression.tab.cc:1444:37: warning: argument 1 value
'18446744073709551615' exceeds maximum object size 9223372036854775807
[-Walloc-size-larger-than=]
 1444 |      yymsg = (char *) YYSTACK_ALLOC (yyalloc);
      |          

and immediately segfaulted.

I used the following compiler flags:

-flto -fcommon -O3

I noticed that if I reduce the optimization level to -O2, there is no segfault.

I did a bisection from

commit f47f687a97260b1a1305cbf2d7ee3d74b2916a74
Author: Richard Biener <rguenther@suse.de>
Date:   Thu Apr 25 17:58:56 2019 +0000

to:

commit 4945b4c2c8628bdd61b348ea5bd1f9b72537a36e (HEAD)
Author: Martin Liska <mliska@suse.cz>
Date:   Tue May 26 09:01:41 2020 +0200

and I found that the following commit may have introduced the error:

commit ff6686d2e5f797d6c6a36ad14a7084bc1dc350e4
Author: Martin Jambor <mjambor@suse.cz>
Date:   Fri Sep 20 00:25:04 2019 +0200

I am not sure if this is a known issue or if I'm doing something wrong. 

This is the latest GCC version that I know reproduces the error:

[eochoa@osprey1 ~]$ $HOME/code/gcc-inst/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/home/eochoa/code/gcc-inst/bin/gcc
COLLECT_LTO_WRAPPER=/home/eochoa/code/gcc-inst/libexec/gcc/aarch64-unknown-linux-gnu/11.0.0/lto-wrapper
Target: aarch64-unknown-linux-gnu
Configured with: /home/eochoa/code/gcc/configure --disable-bootstrap
--disable-libsanitizer --enable-__cxa_atexit --enable-shared
--disable-libsanitizer --enable-languages=c,c++,fortran --enable-lto
--enable-gold --enable-linker-build-id --with-cpu-emag
--prefix=/home/eochoa/code/gcc-inst/
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.0.0 20200526 (experimental) (GCC)

[0] https://gcc.gnu.org/gcc-10/porting_to.html

             reply	other threads:[~2020-05-26 14:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 14:49 erick.ochoa@theobroma-systems.com [this message]
2020-05-26 15:08 ` [Bug ipa/95336] " pinskia at gcc dot gnu.org
2020-05-26 15:38 ` erick.ochoa@theobroma-systems.com
2020-05-26 15:48 ` erick.ochoa@theobroma-systems.com
2020-05-26 15:54 ` [Bug target/95336] " pinskia at gcc dot gnu.org
2020-05-26 16:23 ` erick.ochoa@theobroma-systems.com
2020-05-26 18:18 ` jamborm at gcc dot gnu.org
2020-05-26 20:12 ` erick.ochoa@theobroma-systems.com
2020-05-27  7:33 ` [Bug target/95336] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-05-27 11:41 ` marxin at gcc dot gnu.org
2020-05-27 11:51 ` erick.ochoa@theobroma-systems.com
2020-05-27 12:00 ` marxin 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-95336-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).