Darius Galis’s ポイント | Open Source Tools for Renesas

Darius Galis’s ポイント

Darius Galis 426 ポイント.

フォロー

Darius Galis's ポイント

Total 426

0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0

+10

7月 2, 2020 Answered Can CC-RX linker link to GCC-RX built static library?

+10

7月 2, 2020 Answered How to install libgen for GNU Arm Embedded on Linux host

+1

7月 1, 2020 Commented Hello, Could you please give us more information about the errors received? For example the error messages and the steps at which you encounter them? Thank you very much, The GNU Tools Team

+10

6月 29, 2020 Answered binutils-2.24_2019Q2 rebuilding method

+1

5月 26, 2020 Commented Hello, Thank you for the quick answer. While the information provided is useful, it doesn't help getting to the root of the issue. This was the reason why we kindly asked you to open a private support ticket in which you should attach the ENTIRE e2studio project. It contains all the information needed to assess the generation of this undesirable behavior either through project-related configurations or specific code instructions (eg: vector table loading, not defining, at a wrong address). Thank you for your understanding, The GNU Tools Team

+1

5月 25, 2020 Commented Hello, Thank you for reaching out to us! The "No source available" message is usually generated when the project is built without any debug information option enabled. We suggest checking the Project's Debug Settings to be set at least as Debug level of -g2 and if the entry point is set correctly or the vector table is loaded at the correct address. If all those settings are correct, and the issue still persists we encourage you to open a private support ticket on our platform in which you can attach your project in order for us to investigate the issue more closely. Regarding the volatile question, we would like to ask you for more details about what you are trying to achieve by disabling the optimization for every variable. The GCC compiler does not have an option that sets all variables as volatile, but it supports options that disable certain optimization passes. If you can provide us with some explanation about why you are needing this option, we might be able to offer more in-depth support. We are looking forward to hearing from you, The GNU Tools Team

+10

5月 19, 2020 Answered GCC 8.3.0.202002-GNURX the stack usage calculation is still incorrect

+1

2月 25, 2020 Commented Hello, Unlike CCRL/IAR, the GCC RL78 doesn't use the __far attribute for instructions that will be saved in the code section. In fact, in GCC this is not possible because the standard defines named address spaces only for data sections (please see the following: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1275.pdf ). In order to handle code bigger than 64 KB, GCC uses a PLT (Procedure Linkage Table) to achieve this feat. A good explanation about this can be found here: https://www.technovelty.org/linux/plt-and-got-the-key-to-code-sharing-and-dynamic-libraries.html . Although the article is about dynamic libraries, the same principle can be applied. Please observe the key part of the article: "The indirection used here is called a procedure linkage table or PLT. Code does not call an external function directly, but only via a PLT stub. Let's examine this..." Please let us know if we can be of further assistance, Best Regards, The GNU Tools Team

+1

1月 23, 2020 Commented Hello, When changing the if value from 0 to 1, the compiler optimizes out the memset call since it is not used afterwards. You can see this by compiling lib.c with the -S option instead of -c and investigating the assembler file generated. Since there is no memset call anymore, the linker is now able to successfully link the generated library. Best Regards, The GNU Tools Team

+10

1月 21, 2020 Answered “undefined reference to `memset’” bug

+1

12月 5, 2019 Commented Hello, Our next planned release of the GCC RX toolchain is scheduled for the end of April 2020. After releasing the toolchain we will announce every customer personally if their submitted issue is solved. Thank you for your understanding. The GNU Tools Team

+1

12月 3, 2019 Commented Dear customer, We are happy to report that this issue should be resolved in the new 2019q4 release of the GCC for Renesas RX toolchain, present on our website for download at: https://gcc-renesas.com/downloads/download.php?f=rx/8.3.0.201904/gcc-8.3.0.201904-GNURX-ELF.exe If you have any further questions about the issue, please let us know. – Thank you, The GNU Tools Team

+10

11月 28, 2019 Answered GCC for Renesas RX 4.8.4.201803-GNURX-ELF toolchain issue

+1

9月 27, 2019 Commented Hello, We encourage you, if you did not already do that, to download the GNUM16CM32 toolchain from our platform (available here: https://gcc-renesas.com/m16c-legacy-toolchains/). After installing it, you will find the documentation regarding the Migration Guide in the /Doc/Renesas-GNUM16CM32C-Migration-Guide.html. This guide explains the differences between the compiler and it has nothing to do with make files. The same installation folder will also provide sample projects that can be integrated in the HEW IDE (available here: https://www.renesas.com/us/en/software/D1015689.html). We also have a dedicated page for Getting Started with HEW, which you can find here: https://gcc-renesas.com/getting-started/hew/index.html . You can find additional information about the makefiles here: https://www.tutorialspoint.com/makefile/index.htm or here: https://www3.ntu.edu.sg/home/ehchua/programming/cpp/gcc_make.html If there is anything more we can assist you with, please do not hesitate to contact us. Best regards, The GNU Tools Team

+10

8月 27, 2019 Answered HEW still available for download?

+10

8月 20, 2019 Answered Program lost

+10

8月 6, 2019 Answered The program is lost

+1

7月 31, 2019 Commented Hello, In order to debug the library function, you can use the Instruction Stepping Mode (from Menu Bar → Run → Instruction Stepping Mode) after you start debugging your project. This feature allows the investigation of the sprintf function assembly code step by step. Unfortunately, we were unable to reproduce the issue with a basic sample project. Before we ask to send us a project, could you please verify that the .istack and .ustack sections are being initialized with an address that is a multiple of 4 bytes? You will find those sections defined in your project linker script, usually found in your /generate folder as: e.g: .ustack 0x200: AT(0x200) { _ustack = .; } > RAM .istack 0x100: AT(0x100) { _istack = .; } > RAM If this suggestion does not work, we encourage you to open a private support ticket in which you can attach your sample project for us to investigate. Looking forward to your reply, – Best regards, The GNU Tools Team

+10

7月 30, 2019 Answered GCC RX231 Printf problem

+10

7月 8, 2019 Answered 4.8.4.201902-SP1-GNURX support device?

« 前へ 1 2 3 4 5 次へ »

サポート