Michael, Thanks for making me aware of the issues filed to the GCC bug tracking system. I will have a discussion with our uP team to determine how to get items resolved. I don't know the history of all of this, but I can at least see about altering the present.
> -----Original Message----- > From: [email protected] [mailto:devel- > [email protected]] On Behalf Of Michael Walle > Sent: Thursday, February 09, 2012 12:46 AM > To: Milkymist developers' list > Subject: Re: [Milkymist-devel] Clang/LLVM > > On Thu, February 9, 2012 00:47, Johnathan Mantey wrote: > > It's important to remember that Lattice Semiconductor is the official > > maintainer of the LM32 GCC code that gets fed back into the mainline tool. > > We need to be aware of problems with the compiler results in order to > > correct issues with the GCC code. If the MM community knows of issues > > and is not reporting them to us the GCC tools are never going to be > corrected. > > IMO, GCC is the 800 pound gorilla of the C development tools within > > the FOSS realm. It's important for Lattice to make sure the GCC tool > > emits code that makes the LM32 do the right thing. I recommend that > > any bugs that are known to exist as a result of MM development be sent > > to [email protected]. It will benefit you by making the > > LM32 perform the code you've written, and it will benefit every other > > LM32 user as well. > > Hi Johnathan, > > all (known) bugs are filed in the gcc bugzilla system and your maintainer was > contacted serveral times (by me and i would guess sebastien, too). But nothing > happened, but some empty promises. > > At least for me, this is one reason for my disappointment. > > -- > michael > > _______________________________________________ > http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org > IRC: #milkymist@Freenode _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
