Open Source Tools Support’s reputation

Open Source Tools Support's reputation

Total 638

0,0,0,0,0,0,0,0,0,0,0,0,0,10,0,0,10,0,0,0,0,0,0,0,1,0,0,1

June 28, 2016 Commented Hi again, Just to clarify, please let us know: when you had upgraded the components, did you reinstall version 5.0.1.005 from scratch? That is the recommended approach to upgrading e2 Studio, just so that there are no remnants or leftovers from a previous version, which may affect functionality otherwise after the upgrade. Nonetheless, the warning message is not the issue here. That is just a notice, but should not affect functionality. You also mentioned: >>On step 5 there was no debug perspective, perhaps that is a clue? The perspective had disappeared because you have deleted the .metadata folder in the workspace. There will not be any new debug perspective created successfully, until you are able to launch a successful debug again. Let us know please if this helps. -- Thank you, The GNU Tools Support Team

June 28, 2016 Commented Hello Adam, The error message displayed by e2 Studio below: >>Warning: the current language does not match this frame. seems to be the normal behavior for the e2 Studio environment, as the IDE needs to do background processing in order to determine if the current programming language in use is the C language or otherwise. Did this continue to happen, or does it continue to happen on a regular basis, preventing the proper usage of e2 Studio? If so, please let me know the exact steps you have taken, so we can try to reproduce the issue on our end and provide further assistance/feedback. -- Thank you, The GNU Tools Support Team

June 24, 2016 Commented 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

June 24, 2016 Commented Hi, Just to clarify - we are going to resolve this issue in a future release, and it has been already classified as a bug in our roadmap as of now. Also, in order to choose what library is being used in your project, please go to Project Properties -> Library Generator -> Settings -> Select library (newlib/optimized). -- Kind regards, The GNU Tools Support Team

+10

June 24, 2016 Answered Why does rand() return (max) 32767 when RAND_MAX is defined as 0x7fffffff?

+10

June 24, 2016 Answered Eclipse and GNU tools

June 24, 2016 Commented Hi Adam, Just checking in to see if you still need us to keep this open, or if you had submitted the project already in a private support request? -- Thank you, The GNU Tools Support Team

June 23, 2016 Commented Hello Olivier, Thank you for your feedback! This is a confirmation message to let you know that we have received your request and that we are looking into it as soon as possible. We will be getting back to you soon with our findings. -- Thank you, The GNU Tools Support Team

June 22, 2016 Commented 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

+10

June 22, 2016 Answered GNUARM-NONEV16.01-EABI Compiler Crash

June 17, 2016 Commented Hello John, The problem is that the SHC toolchain does not fully comply with the DWARF standard - this is why a conversion step is needed to help remove those incompatibles. Unfortunately, sh-elf-gdb will not be fixed as a result thereof. We hope this helps. -- Kind regards, The GNU Tools Support Team

+10

June 8, 2016 Answered Bad link for: https://llvm-gcc-renesas.com/manuals/SH-ABI-Specification.html

June 8, 2016 Commented Hi Adam, >> Do you also want me to include samples that make the compiler crash too? Yes please, this will help us track down the problem easier and faster. >> Or are these errors outside the scope of E2Studio and in the realm of machine virtual memory settings? The GCC compiler is designed to cope with very large files efficiently. Nonetheless, we will differentially check the cause of the memory allocation crash and, once a problem is found, try to come up with a fix for it as soon as possible. -- Thank you, The GNU Tools Support Team

+10

June 3, 2016 Answered kpit forum database

June 2, 2016 Commented Hi Adam, Thanks again for your detailed response! I just wanted to let you know that we have identified a number of problems in e2 Studio and we are working on a solution for all of them with the e2 Studio team. Just to be sure that we do not miss any of the issues/errors you are experiencing, could you please: a) prepare all the build logs where you are experiencing them, and... b) send them to us for detailed analysis, pinpointing the problems in each? This way, we can ensure a qualitative release which will most likely resolve all of the above. -- Thank you, The GNU Tools Support Team

May 24, 2016 Commented Hello Adam, Please let us know if we have answered your question in full or if you need any further assistance from us. If we do not receive any feedback within 24 hours, this thread will be closed, but may be re-opened later on if needed. -- Thank you, The GNU Tools Support Team

May 20, 2016 Commented Hello Adam, We hope your question has been answered. Please let us know if we can be of any further assistance, or if we can close this thread otherwise. This thread will be closed if no reply is received 24 hours after this message, but can be reopened upon request. -- Thank you, The GNU Tools Support Team

+10

May 17, 2016 Answered Will there be 64-bit binaries available for Linux in the future (including iodefines) and/or a simple tar.gz/tar.bz2 package?

May 16, 2016 Commented Hello Adam, Thank you for the feedback. >>Are there any release notes for libstdc++ to indicated the differences between the V14.02 and V16.01 tool chains? You can find the release notes for the toolchains in their installation folder (e.g: C:\Program Files (x86)\KPIT\GNUARM-NONEv16.01-EABI\). There is a file named release_notes.pdf. No information is provided there for libstc++, but you have information about the gcc version. If you are still using the GNUARM-NONE v14.02 you can find the documentation for gcc here: https://gcc.gnu.org/gcc-4.9/ > GCC 4.9.2 October 30, 2014 (changes, documentation). If you click on 'changes' you will be redirected to the gcc 4.9 release notes and you will see the libstc++ part at the "New Languages and Language specific improvements" chapter. The manual for the C++ library is here: https://gcc.gnu.org/onlinedocs/gcc-4.9.2/libstdc++/manual/ and the reference manual is here: https://gcc.gnu.org/onlinedocs/gcc-4.9.2/libstdc++/api/ If you switched to the GNUARM-NONE v16.01, you can find the documentation for gcc here: https://gcc.gnu.org/gcc-5/ > GCC 5.2 July 16, 2015 (changes, documentation). If you click on 'changes' you will be redirected to the gcc 5.2 release notes and you will see the libstc++ part at the "New Languages and Language specific improvements" chapter. The manual for the C++ library is here: https://gcc.gnu.org/onlinedocs/gcc-5.2.0/libstdc++/manual/ and the library reference manual is here: https://gcc.gnu.org/onlinedocs/gcc-5.2.0/libstdc++/api/ >>So I uninstalled V16.01, Close E2Studio, reverted the project. Then when I re-opened the project, E2Studio unregistered the tool chain then reported that V16.01 was missing and it would use V14.02. If you want to change the toolchain version, you can right-click on your project > Renesas Tool Settings > Change Toolchain Version (from the C/C++ Build tab); Alternatively, you can click on the Renesas Tool Settings button from your second menu bar > Change Toolchain Version (from the C/C++ Build tab); ...or, click on your project, then alt+T > Change Toolchain Version (from the C/C++ Build tab); >>C:\Program Files (x86)\KPIT\GNUARM-NONEv16.01-EABI\arm-none-eabi\arm-none-eabi\arm-none-eabi\lib\armv7-ar\thumb\fpu\” folder there is a libstdc++.a file. >>-L“C:\PROGRA~2\KPIT\GNUARM~2.01-\ARM-NO~1\ARM-NO~1/arm-none-eabi/lib/armv7-ar/thumb/fpu? We could not reproduce the problem at our end. If possible and if you may, please send us the project to take a closer look. You can mark this query as private, so nobody else will be able to see your proprietary software code, or you can open a private support request by choosing Support -> New Support Query from the top menus in our site. — Best regards, The GNU Tools Support Team

+10

May 9, 2016 Answered Will there be 64-bit binaries available for Linux in the future (including iodefines) and/or a simple tar.gz/tar.bz2 package?

« Previous 1 2 3 … 6 7 8 9 10 Next »