Linux OpenRISC platform development
 help / color / mirror / Atom feed
From: Philipp Wagner <lists@philipp-wagner.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] Fwd: or1k GCC Internal Compiler Error
Date: Wed, 11 May 2016 17:17:06 +0200	[thread overview]
Message-ID: <57334CF2.6080700@philipp-wagner.com> (raw)
In-Reply-To: <542B2933.4090402@philipp-wagner.com>

Hi,

I've been asked to forward this bug report to the new mailing list; the
bug is still not resolved, so I'd be glad if someone wants to have a
look at it.

Philipp


-------- Forwarded Message --------
Subject: or1k GCC Internal Compiler Error
Date: Wed, 01 Oct 2014 00:05:39 +0200
From: Philipp Wagner <lists@philipp-wagner.com>
To: openrisc@lists.opencores.org

Hi,

we get an Internal Compiler Error (ICE) from the or1k 4.9 and 4.8 GCC
when trying to compile C++ code that makes use of inheritance and
virtual functions. The ICE only occurs if optimization is enabled (-O1
and above), it does *not* happen with -O0. The code also compiles fine
on a regular Ubuntu 14.04 x86_64 GCC 4.8 (probably heavily patched though).

I reduced the attached testcase down to a minimum (it's code from
Fiasco.OC) to show the ICE, but I have no clue what exactly triggers the
problem. Could possibly anybody with more experience in the compiler
field have a look at what might cause the error?

Some free beers at ORConf will be reserved for the solution for that :-)

Philipp



-------------- next part --------------
A non-text attachment was scrubbed...
Name: testcase.cc
Type: text/x-c++src
Size: 2748 bytes
Desc: not available
URL: <http://lists.librecores.org/pipermail/openrisc/attachments/20160511/b9055083/attachment.cc>

           reply	other threads:[~2016-05-11 15:17 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <542B2933.4090402@philipp-wagner.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=57334CF2.6080700@philipp-wagner.com \
    --to=lists@philipp-wagner.com \
    --cc=openrisc@lists.librecores.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