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

Open Source Tools Support’s ポイント

Open Source Tools Support 638 ポイント.

フォロー

Open Source Tools Support's ポイント

Total 638

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

+1

12月 14, 2019 Commented Hello, Thank you for your patience! After a thorough investigation, we concluded that the displayed behavior, even if it resembles a compiler issue, is not constituting a compiler bug. Although... typedef void (*numentry_t)(int cnt, int arg1, …); typedef void (*numentry1_t)(int cnt, int arg1); look similar, they are quite different. While it is true that for both instructions the first argument, int cnt, is saved in R1 as the RX ABI indeed dictates, when it comes to the second argument, things are starting to drift away: For (*numentry1_t)(int cnt, int arg1) the second argument is saved in R2 as expected, but for the (*numentry_t)(int cnt, int arg1, …) instruction, the arg1 is saved into the stack. The reason why this happens is that RX not only passes variable arguments on the stack, but in this case it is also using the second argument (arg1) as a mean for the va_start to locate the first variable argument to save on the stack. This is also mentioned in chapter 7.6 of the ISO/IEC standard: "The rightmost parameter plays a special role in the access mechanism, and will be designated parmN in this description." The same behavior can be seen in other compilers that are built with respect to the same ABI. For example, CCRX is also placing arg1 on the stack in case of a variable list of arguments. Please let us know if we can be of further assistance, __ Best Regards, The GNU Tools Team

+1

12月 14, 2019 Commented Hello, Unfortunately, there are no plans for further developing the Optlib library. Starting with the latest, 2019q4 GCC for Renesas release, the optlib library is considered deprecated. All reasons for this decision are stated in the release notes for both RX and RL78 compilers. We encourage you to start looking for the newlib alternative when taking into consideration new projects. We apologize if this causes any inconvenience, The GNU Tools Team

+1

12月 13, 2019 Commented Dear Frank, Many thanks for your kind words! We sincerely appreciate them. Looking forward to more good things to come in the near future :-) Happy Holidays! __ The GNU Tools Team

+1

12月 13, 2019 Commented Hello, It looks like we ran into a caching issue, which caused the release notes and other pages (including the source code download pages) to not be updated correctly. However, after your report we have reset the cache and now all should show up properly. Thank you for letting us know! __ The GNU Tools Team

+1

12月 11, 2019 Commented Hello Mohd, Thanks for your feedback. There's a number of issues here that we would like to address upfront. 1. First, you had provided a Google link. There is no hard link for download, or a specific URL used. Therefore, it's unclear where the download comes from. 2. We do not offer any level of support for building the toolchain other than our own supported environment, which is fully documented on the gcc-renesas.com platform. For that environment, you may find full instructions on how to proceed with the builds by looking at the build toolchain page. __ Thank you, The GNU Tools Team

+1

12月 10, 2019 Commented Hello Roger, As you have also opened a support ticket for this same issue, and we are continuing to provide support for this through that private ticket, please let us know if you wish to keep this issue open or if we can mark it as closed. __ Thank you, The GNU Tools Team

+1

12月 10, 2019 Commented Hello, The release notes are present in the download page of the toolchain at https://gcc-renesas.com/rl78/rl78-download-toolchains/ (please click the green question mark to the right of every toolchain). We hope this helps, The GNU Tools Team

+1

12月 9, 2019 Commented Dear user, Please be informed that our support for building the toolchain is limited to the environment and settings used by us, and which are thoroughly documented in the build procedure you have used. If you use a different environment or build procedure, we are not able to provide any support. __ Thank you, The GNU Tools Team

+1

12月 6, 2019 Commented Dear Frank, Thank you so much for your support! We're grateful for your kind comments, it's awesome to see great supporters like yourself reaching out and staying in touch. We wish Happy Holidays to all our users! The GNU Tools Team

+1

11月 1, 2019 Commented Hello, Thank you for reaching out to us! Unfortunately, we were unable to reproduce the issue with a basic sample testcase. Could you please send us a sample project in which the issue is reproducible in order to investigate? We encourage you to please open a private support ticket where you could attach the project. __ Best regards, The GNU Tools Team

+1

11月 1, 2019 Commented Hi Vikram_FE, we're looking into your issue and will reply as soon as we have an update.

+1

10月 14, 2019 Commented You need to please install the toolchain first, then open up a recent version of e2Studio and the toolchain should be automatically detected. Just in case the automatic detection fails, you may also go to e2Studio and click the Help menu, then choose "Add Renesas Toolchains".

+1

9月 26, 2019 Commented Hello, Thank you for reaching out to us! Could you please let us know the target device (RX, RL78, ARM) that you need help with? We also suggest to use the e2studio IDE (available for download here: https://www.renesas.com/in/en/products/software-tools/tools/ide/e2studio.html) in order to generate simple sample projects for your device of choosing. We look forward to hearing back from you soon. __ Best regards, The GNU Tools Team

+1

3月 23, 2019 Commented Thank you very much for sharing your solution with the rest of the users of our toolchains! We are happy you were able to find the solution eventually. As you may guess, with the various Linux distributions, and their highly different package repositories, it is quite difficult to ensure full compatibility with all such platforms, which is why we always appreciate any feedback from users that can explain how they were able to install the toolchains with no issues. We thank you for that, and hope other users will find this useful as well. Should you have any other questions or concerns, please feel free to let us know at any time. -- Thank you, The GNU Tools Team

+1

3月 23, 2019 Commented Hi, Thank you for reaching out! Could you please verify that: a) you have executable permissions enabled for the file? If not, please assign them as follows: $>chmod +x gcc-4.8.4.201803-GNURX-ELF.run b) you are executing the installer as: $>./gcc-4.8.4.201803-GNURX-ELF.run c) do you still get the same error when attempting to run the installer as above? Please let us know and we would be happy to assist the best we can. __ Thank you, The GNU Tools Team

+1

3月 18, 2019 Commented Dear customer, One of our technical support representatives has touched base with you at the time of the question. We are going to close this thread therefore, as we are confident the issue had been resolved by now. Should you desire to ask anything else, please feel free to open another issue or create a new support ticket. __ Thank you, The GNU Tools Team

+10

3月 8, 2019 Answered Can you please give more details on the Bug-Fixes in your release descriptions?

+1

2月 14, 2019 Commented Hello, Please let us know, how are you attempting to execute the installer after assigning it executable rights? Thank you, The GNU Tools Team

+1

2月 14, 2019 Commented Thank you @edge30 for the comment. Yes, that's correct, to install the toolchain, please download the ".run" file, change its permissions to include executable rights (e.g. $ chmod +x ) and then execute it directly.

+1

2月 1, 2019 Commented Hello, Yes, you are correct, it is -misa=v2. We apologize for any confusion this may have caused. __ Thank you, The GNU Tools Team

« 前へ 1 2 3 4 5 6 7 8 9 10 次へ »

サポート