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

+1

7月 5, 2019 Commented Hello, We investigated this issue and found out that the loop invariants algorithm seems to be causing the issue. We suggest disabling it by using the -fno-move-loop-invariants option. We also want to inform you that we are working on a fix for this, which will be available in one of the next releases. Thank you for your understanding! – Best regards, The GNU Tools Team

+1

7月 5, 2019 Commented Hello, Thank you for your valuable input! We had taken your proposal into consideration, and starting with the 2019q2 GCC releases we added more relevant information in our release notes. Please let us know if we can be of further assistance! __ Thank you, The GNU Tools Team

+1

6月 29, 2019 Commented Hello, We are currently investigating which algorithm, from the ones employed by the code size optimization (-Os) option, is the culprit. In the meantime, we suggest one of the following: 1. You could change the optimization level to -O0 (none) for that specific file in which the function resides by right-clicking on the file → Properties → C/C++ Build → Settings → Compiler → Source → User defined compiler options. 2. Add the optimize attribute to the function prototype: uint32_t test(void) __attribute((optimize("-O0"))); uint32_t test(void) { ... } This will ensure that only that function will be compiled without any optimization flags. We are sorry for any inconvenience caused. – Best regards, The GNU Tools Team

+5

6月 28, 2019 Up vote 回答 Is this a bug in GCC?

+10

6月 27, 2019 Answered Is this a bug in GCC?

+5

6月 25, 2019 Up vote 回答 about ABI of Renesas RX

+10

6月 24, 2019 Answered about ABI of Renesas RX

+1

5月 13, 2019 Commented Hello, Thank you for your patience! A fix for this issue is available starting with the GCC for Renesas 4.9.2.201801-GNURL78 toolchain version. – Best regards, The GNU Tools Team

+10

7月 1, 2018 Answered compiling relocatable libs rl78/g13 gcc e2-studio

+1

6月 16, 2018 Commented Hello, In your example you have the following: The .data section is loaded at _mdata address (see the AT directive) which is part of ROM (it is usually instantiated as the last address of the .tors section which is part of ROM), but its virtual memory address is set in RAM. That means that the section is loaded in ROM, starting with the _mdata address, but when the executable is ran, the .data section will have its starting address at 0x204. Same it is with the CopiedFunctions section. It will be in the ROM at load time (AT (_mdata + _edata)), respectively in RAM at run time, starting with the _CopiedFunctions address. If you want your section to be in ROM at run time also, you must specify the VMA address to ROM, which is, using your example: .CopiedFunctions : AT (_mdata + _edata) { _CopiedFunctions = .; *(..CopiedFunctions) _endCopiedFunctions = .; } > ROM Please let us know if we can be of further assistance. Best Regards, The GNU Tools Team

+10

6月 14, 2018 Answered Debug Functions copied to RAM

+5

6月 7, 2018 Up vote 回答 Dose rl78-elf-ld support g10 processor?

+10

6月 7, 2018 Answered Dose rl78-elf-ld support g10 processor?

+5

5月 12, 2018 Up vote 回答 Can I use “new” operator?

+10

5月 12, 2018 Answered Can I use “new” operator?

+1

4月 26, 2018 Commented Hello, The last HEW supported RX toolchain version was the RX 14.01 version which can be found here: https://gcc-renesas.com/downloads/download.php?f=rx/14.01/GNURXv1401-ELF.exe. Unfortunately, we don't offer HEW support anymore and we suggest to upgrade to the e2studio IDE if you want to use our latest toolchain releases. The e2studio IDE can be downloaded from the renesas page: https://www.renesas.com/en-us/products/software-tools/tools/ide/e2studio.html?campaign=mc_b_e2s_rs_00002#downloads. Nonetheless, if you prefer using HEW, the RX 14.01 versions (and below) will ask you when installed if you want to integrate them in the HEW IDE. We suggest to choose the Custom Installation to make sure you are prompted with the HEW integration checkbox. Please let us know if we can be of further assistance. __ Best regards, The GNU Tools Team

+1

3月 19, 2018 Commented Hello, Thank you for providing this information. Based on your issue, we decided to take in consideration adding the stack initialization subroutine into the files generated. Until then, we suggest the following workaround: Please create a CC-RL project for your device and copy the _stkinit function from the stkinit.asm into the start.S generated by the GCC compiler. Since the CC-RL saves the stackend address before calling stkinit, you should also define the stackend address (we defined it in the linkerscript, in the stack section as _stackend = _stack - stack_size). We prepared a start.S example used for a R5F1006A device here: https://gcc-renesas.com/uploads/bvFJ42tXjTQwr14R/start.S Please let us know if that works for you. Best regards, The GNU Tools Team

+10

3月 16, 2018 Answered Stack initialization assembly code

+1

2月 18, 2018 Commented Hello, Thank you for providing this information. We would like to inquire more details about the issue. Could you please provide the build log and provide any additional information that might be relevant to this issue? Thank you for your cooperation. – Best regards, The GNU Tools Team

+10

2月 16, 2018 Answered GCC for Renesas RL78: how to fix ‘undefined reference to memcpy’

« 前へ 1 2 3 4 5 次へ »

サポート