Displaying 4 results from an estimated 4 matches for "pr263".
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
...rt 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...
2004 Jul 15
3
[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
2004 Jul 15
2
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
...xt 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 cos...
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
...l 2004, Reid Spencer wrote:
> > 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.
This has no impact on the users at all... it has an impact on the
maintainers of the LLVM .bc file...