Hi, Thank you for your comment.
>>Is this for some kind of legacy backwards compatibility of something? Sort of, this is required by the following tool https://www.renesas.com/en-eu/products/software-tools/tools/code-generator/ap4-application-leading-tool-applilet.html There are not many plans to improve this tool and other solutions (which might be more complex) might not be possible to implement in this tool. >>There are ways how to achieve the same with standard C and C++ language The only way I can think of is to put the variable in a separate section (using section attribute) and then in the linker script put that section at the desired address. The problem is AP4 does not touch the linker script it only generates source code. Do you have any other ideas/suggestions? I'm very happy to listen. Best Regards, Sebastian -----Original Message----- From: Oleg Endo [mailto:oleg.e...@t-online.de] Sent: 05 January 2018 11:59 To: Sebastian Perta <sebastian.pe...@renesas.com>; gcc-patches@gcc.gnu.org Subject: Re: [PATCH] RX pragma address Hi, On Fri, 2018-01-05 at 11:03 +0000, Sebastian Perta wrote: > > Hello, > > The following patch adds a new pragma, "pragma address" for RX. > The patch updates extend.texi and add a test case to the regression > as well. > For the test case I checked than test is getting picked up in gcc.log > unfortunately for the .texi part I don't know where to look/what to > do to > get the > documentation generated. > > This is similar to the pragma address implemented for M32C. Is this for some kind of legacy backwards compatibility of something? There are ways how to achieve the same with standard C and C++ language features ... so I was wondering what's the purpose of this? Cheers, Oleg
