Reid Spencer
2004-Jul-15 22:33 UTC
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004 17:43:27 -0500 (CDT) Chris Lattner <sabre at nondot.org> wrote:> Sorry! LLVM 1.3 will probably be out in a few weeks...Speaking of which, what are your intentions for 1.3? Are you waiting on CPR? Anything else? We're starting to get some traction with more developers and I think doing a release sooner rather than later might be worth it for all parties involved. Reid
Chris Lattner
2004-Jul-15 22:57 UTC
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004, Reid Spencer wrote:> On Thu, 15 Jul 2004 17:43:27 -0500 (CDT) > Chris Lattner <sabre at nondot.org> wrote: > > Sorry! LLVM 1.3 will probably be out in a few weeks... > > Speaking of which, what are your intentions for 1.3? Are you waiting on CPR? > Anything else? We're starting to get some traction with more developers and > I think doing a release sooner rather than later might be worth it for all > parties involved.CPR would be really nice. There is also this ephemeral PPC support that may or may not make it, but would be really awesome it if did. I would also like to turn on some sort of interprocedural alias analysis by default (for performance). Another thing that is on my short list for 1.3 is to get as many .bc format changes out of the way as possible so the backwards compat code in the .bc reader is simpler. In particular, I would at least like to get placeholders for PR263 and maybe PR400. Personally I think that we've waited much too long for the 1.3 release, but there is a cost to doing to testing and packaging for a release. This responsibility usually falls on John Criswell's shoulders, so we try to fit these things into his schedule. :) In my personal view of the world, I think that 2 or 3 months between a release is about right. Thoughts? -Chris -- http://llvm.cs.uiuc.edu/ http://nondot.org/sabre/
Reid Spencer
2004-Jul-15 22:58 UTC
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004 17:57:20 -0500 (CDT) Chris Lattner <sabre at nondot.org> wrote:> CPR would be really nice. There is also this ephemeral PPC support that > may or may not make it, but would be really awesome it if did. I would > also like to turn on some sort of interprocedural alias analysis by > default (for performance).CPR might make it in the next couple of weeks. Depends on my time availability and how many nasty bugs I run into. Do you really think a viable PPC be is doable in a couple of weeks? Lawyers being what they are, I doubt they'll dot the i's and cross the t's before the next couple of weeks. as for IAA, sounds great.> Another thing that is on my short list for 1.3 is to get as many .bc > format changes out of the way as possible so the backwards compat code in > the .bc reader is simpler. In particular, I would at least like to get > placeholders for PR263 and maybe PR400.This I strongly agree with. We need to minimize impact to end users. I'll do what I can but I think CPR is a higher value target so will focus on that first.> Personally I think that we've waited much too long for the 1.3 release,me too :(> but there is a cost to doing to testing and packaging for a release. > This responsibility usually falls on John Criswell's shoulders, so we try > to fit these things into his schedule.Hmm. I think that kinda needs to change, especially as number of LLVM developers goes. Everyone needs to get involved just before a release and test, test, fix, test. Testing should be divied up (especially known problems). Developers should be assigned to expand/strengthen testing in areas new to the release, etc. Leaving it in one person's hands is both a bottleneck and kinda unfair to John (unless he's a masochist)> :) In my personal view of the > world, I think that 2 or 3 months between a release is about right.4 releases per year is pretty standard. 1 per quarter. Certainly the frequency shouldn't be less unless there is some strong need or a given release proves problematic to test, but 1ce per quarter suits me well.> > Thoughts?Now you have them :) Reid
Chris Lattner
2004-Jul-15 23:05 UTC
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004, Chris Lattner wrote:> Personally I think that we've waited much too long for the 1.3 release,BTW, for those who are interested in the differences between 1.2 and CVS, check out: http://llvm.cs.uiuc.edu/docs/ReleaseNotes.html#whatsnew Note that the release notes still need to be polished, but you'll get the basic idea. -Chris -- http://llvm.cs.uiuc.edu/ http://nondot.org/sabre/
Seemingly Similar Threads
- [LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
- [LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
- [LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
- [LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
- [LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)