GNUARM-NONEV16.01-EABI Compiler Crash

Question

GCC Support

0

afull 42 Rep. Wed, Jun 22, 2016, 13:55:22 UTC

Hi,

Linked below is a project that demonstrates the following compiler crash:

Compiler Crash

(http://www.ardware.co.uk/compilercrash.zip)

cc1plus.exe: out of memory allocating 107868728 bytes
src/subdir.mk:18: recipe for target ‘src/modules2.o’ failed
make: *** [src/modules2.o] Error 1

Compiles OK without optimisation.

Best regards,

Adam.

Andreea Petian answered Mon, Feb 27, 2017, 14:33:32 UTC

4 answers

score 0 · Answer 1 · 2017-02-27T14:33:32+00:00

0

Andreea Petian 66 Rep. Mon, Feb 27, 2017, 14:33:32 UTC

Hello Adam,

In order to use a toolchain from GNU ARM Embedded instead of the one you are using now, you will have to convert your project from KPIT GNUARM to GNU ARM EMBEDDED.

To convert your project follow the next steps:

1. File → Import.
2. Select: Import KPIT GNUARM Project to GNU ARM Embedded and click Next.
3. Click Browse and select your project.
4. Click Finish.

Unfortunately, for now, we do not provide support for the latest toolchain from Launchpad. That functionality will be available starting with e2studio 6.0.

If you have any other questions, please let us know.

—
Thank you,
The GNU Tools Team

Andreea Petian edited comment on answer Mon, Mar 20, 2017, 15:08:00 UTC

afull - Mon, Feb 27, 2017, 19:47:23 UTC

Hi Andreea,

Thank you. I will give it a go and let you know how I get on.

Best regards,

Adam.
afull - Tue, Feb 28, 2017, 9:48:33 UTC

Hi Andreea,

The link does not work for me. I get:

BlobNotFoundThe specified blob does not exist.
RequestId:dff1b4a4-0001-00dc-04a7-91d56b000000
Time:2017-02-28T09:46:23.5762900Z

Did you check the link before you posted the comment?

Best regards,

Adam.
Andreea Petian - Tue, Feb 28, 2017, 13:03:29 UTC

Hi Adam,

We are sorry for the inconvenience.

The link we provided was pointing to the latest released toolchain for GNU ARM Embedded, by Launchpad. It would seem that it’s now temporarily unavailable.

We will keep an eye on this and let you know when the link becomes available again.

—
Thank you
The GNU Tools Team
afull - Fri, Mar 17, 2017, 8:37:12 UTC

Hi Andreea,

Yes that indeed fixes the compiler crash. However there appear to be significant differences between the tool chains run time libraries which means it fails to link.

It is not a straight forward task to switch tool chains like this!

Any idea when this fix will be available for the KPIT tool chain?

Best regards,

Adam.
Andreea Petian - Mon, Mar 20, 2017, 15:06:30 UTC

Hi Adam,

GNUARM-NONEV16.01-EABI is the latest available version of ARM toolchain released by KPIT.
Unfortunately, no further releases of GNUARM-NONE toolchain will be made.

The only solution is to convert your project from GNUARM-NONE to GCC ARM Embedded using the current project converter.

However,as stated in a previous comment, the latest toolchain from GNUARM Embedded cannot be integrated in e2studio 5.3 .

You can still convert your GNUARM-NONE project to a GNUARM Embeddded project that uses a toolchain version 5.4 or older, but the compiler crash bug is not fixed in any of those versions.

The integration problem will be fixed in the e2studio 6.0 release and the converter will have support for gnu-arm-none-eabi-6-2017-q1.

Please let us know if there is anything else we can help you with.

—
Thank you
The GNU Tools Team

score 0 · Answer 2 · 2017-02-26T19:27:18+00:00

Hello Adam,

We appreciate your patience. As you know, this problem was out of our hands the entire time, but we did reach out to the team capable of handling it and they have now confirmed to us that it has been resolved in the latest release of the toolchain. We have also verified the issue and it seems to be, indeed, fixed.

If you want to try it on your own, please download the toolchain from the following link: http://bit.ly/2mlCn8F

Please let us know if there is anything else we can help you with.

—
Thank you,
The GNU Tools Team

score 0 · Answer 3 · 2016-07-04T11:30:50+00:00

Hello Adam,

Thank you for your patience much appreciated!

Regarding your issue with the latest version of the compiler, at the moment we can confirm that the issue is still persistent.

While we are trying to resolve the bug, as a workaround, please change the optimization level and use either -O0, or -O1. You can change the optimization level on a global scale, for the entire project (by right-clicking on your file, Properties, C/C++ Build, Settings, Optimization and then adjusting the Optimization level via the drop down menu at the top right, then clicking Apply), or for a particular file (by right-clicking the file and following similar steps). We were able to successfully compile the project with either of the two options presented.

—
Thank you,
The GNU Tools Support Team

score 0 · Answer 4 · 2016-06-22T14:17:14+00:00

0

Open Source Tools Support 754 Rep. Wed, Jun 22, 2016, 14:17:14 UTC

Hello,

Thank you for your report! This will help us greatly in expediting the fix for the issue you have experienced.

One question however: is the code proprietary? If so, we can mark this query as private, so it is only available to our staff and to you – so that nobody else will be able to access that URL with the download.

—
Thank you,
Ciprian
The GNU Tools Support Team

Open Source Tools Support commented on answer Thu, Nov 17, 2016, 23:21:18 UTC

afull - Wed, Jun 22, 2016, 14:21:41 UTC

Hi,

The code is open source so it can remain public.

Best regards,

Adam.
Open Source Tools Support - Wed, Jun 22, 2016, 14:23:56 UTC

Hi Adam,

Thank you – we are currently looking into reproducing this issue and resolving it, as soon as possible.

We will keep you updated on this thread.

—
Kind regards,
Ciprian
The GNU Tools Support Team
Open Source Tools Support - Fri, Jun 24, 2016, 16:40:04 UTC

Hi Adam,

Just wanted to let you know that we were able to reproduce the issue you have mentioned, and now we are working on trying to see if the problem is still reproducible with the latest version of the compiler. If the issue is still persistent, we will be issuing an update and a fix for it.

—
Kind regards,
The GNU Tools Support Team
afull - Thu, Nov 17, 2016, 9:29:49 UTC

Hi,

Has there been any progress on this bug?

Best regards,

Adam.
Open Source Tools Support - Thu, Nov 17, 2016, 23:21:18 UTC

Hello Adam,

Thank you for your patience in resolving this matter. Unfortunately, due to circumstances outside our control, this issue is still pending – although actively being worked on at this time. As soon as this is ready, we will inform you of course.

—
Thank you,
The GNU Tools Team