Hi Josef,
Thanks for reporting this problem, and providing a patch to fix it.
I have checked your patch in, along with one, very very minor change
to the formatting of the comment in gen_prefix().
Cheers
Nick
On 19/05/2017 04:13, Martin Sebor wrote:
On 05/18/2017 10:14 AM, Jozef Lawrynowicz wrote:
A patch for this bug was originally posted here:
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01054.html
There were some issues with that patch which I've now fixed.
The MSP430 target supports the automat
On 05/18/2017 10:14 AM, Jozef Lawrynowicz wrote:
A patch for this bug was originally posted here:
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01054.html
There were some issues with that patch which I've now fixed.
The MSP430 target supports the automatic placement of functions and
data in diff
A patch for this bug was originally posted here:
https://gcc.gnu.org/ml/gcc-patches/2017-02/msg01054.html
There were some issues with that patch which I've now fixed.
The MSP430 target supports the automatic placement of functions and
data in different memory regions when passing the
"-mdata-regio
ping
The MSP430 target supports the automatic placement of functions and
data in different memory regions when passing the
"-mdata-region=either" and "-mcode-region=either" options.
MSP430x devices support the large memory model, "-mlarge", which
enables 20 bit pointers, however the vector table
The MSP430 target supports the automatic placement of functions and
data in different memory regions when passing the
"-mdata-region=either" and "-mcode-region=either" options.
MSP430x devices support the large memory model, "-mlarge", which
enables 20 bit pointers, however the vector table across