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 target/95336] [10/11 Regression] Bad code gen omnetpp_r aarch64
Date: Wed, 27 May 2020 11:51:21 +0000	[thread overview]
Message-ID: <bug-95336-4-hwedzslXab@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95336-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Erick Ochoa <erick.ochoa@theobroma-systems.com> ---
(In reply to Martin Liška from comment #8)
> I've just tried current gcc-10 branch tip and I can't reproduce it with:
> -mtune=emag -O3 -flto=16
> 
> Can you please attach complete build log?

Hi,

I was able to get rid of the problem. Thanks for all your help and sorry for
opening this ticket. What I believe to be the reason was a mismatch between
gcc-linker or gcc-glibc installed. After rebuilding my toolchain entirely again
(and not just gcc), I have been able to successfully run omnetpp.

  parent reply	other threads:[~2020-05-27 11:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 14:49 [Bug ipa/95336] New: " erick.ochoa@theobroma-systems.com
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 [this message]
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-hwedzslXab@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).