I have discovered a register optimization bug in the latest release of msp430-elf-gcc. What is the best place to submit the issue? Does msp430-elf-gcc have a dedicated bug tracker site or should I submit to https://gcc.gnu.org/bugzilla/ ?
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I have discovered a register optimization bug in the latest release of msp430-elf-gcc. What is the best place to submit the issue? Does msp430-elf-gcc have a dedicated bug tracker site or should I submit to https://gcc.gnu.org/bugzilla/ ?
It may depend on whether you're working with the TI source bundles or the pure upstream sources.
If you are reproducing the problem in msp430-elf built from the GNU repository trunk/master branches (not the TI source bundle), please submit it on https://gcc.gnu.org/bugzilla, even if you also submit it somewhere TI-specific. Some of us only use the upstream versions and it helps us to know when a problem has already been reported and what its status might be.
(Note: That request does not apply to issues due to device-specific headers or linker scripts that GNU does not maintain.)
Good point. I'm running off of TI's bundle (2.01.01.00). I'll have to try out the GNU repositories.
Do you know of anyone doing builds regularly?
Confirmed in upstream version. Here is a link to the bug for better visibility:
Thanks. That looks a little nasty.
FYI, I posted a note in theTI C/C++ Compiler Forum to let them know; the response provides useful information suggesting that it's going to get some attention, and provides instruction to post bug reports in that forum rather than in here in the MSP430 forum.
(Please do still post detailed bug reports for upstream-reproducible issues on GCC's bugzilla; TI's compiler folks don't monitor this forum, and I don't monitor theirs, so it's all still kinda a mess.)
**Attention** This is a public forum