Displaying 20 results from an estimated 300 matches similar to: "[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)"
2004 Jul 15
2
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)
>From: Chris Lattner <sabre at nondot.org>
>Date: Wed, 14 Jul 2004 14:49:01 -0500 (CDT)
>
>There is currently support for building in non-cygwin windows environments
>protected by _MSC_VER. You just need to broaden the scope of the #ifndef
>to include internix.
>
Sorry Chris, but my DataTypes.h.in seems to be outdated (due to I'm porting
LLVM 1.2), so I'm not
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)
On Fri, 16 Jul 2004, Henrik Bach wrote:
> >There is currently support for building in non-cygwin windows environments
> >protected by _MSC_VER. You just need to broaden the scope of the #ifndef
> >to include internix.
> >
>
> Sorry Chris, but my DataTypes.h.in seems to be outdated (due to I'm porting
> LLVM 1.2), so I'm not at the moment able to edit the
2004 Jul 14
1
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
>From: John Criswell <criswell at cs.uiuc.edu>
>Date: Wed, 14 Jul 2004 09:11:03 -0500
>
>
>The DataTypes.h header file is generated by the configure script and placed
>into your build tree. My best guess is that your system's header files do
>not correctly define these macros, so they are missing.
>
I did a search on the build and source trees, but neither
2004 Jul 15
2
[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/
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004 18:05:21 -0500 (CDT)
Chris Lattner <sabre at nondot.org> wrote:
> 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
It might be a good idea to add a check-in script that puts the latest
version of the pending ReleaseNotes.html into the web site directory and
then link
2004 Jul 15
2
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004, Reid Spencer wrote:
> On Thu, 15 Jul 2004 18:05:21 -0500 (CDT)
> Chris Lattner <sabre at nondot.org> wrote:
>
> > 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
>
> It might be a good idea to add a check-in script that puts the latest
>
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
Silly me. Perhaps then just a more prominent link on the main page with
something like a "what's coming in the next release" label ?
Reid.
On Thu, 15 Jul 2004 18:16:33 -0500 (CDT)
Chris Lattner <sabre at nondot.org> wrote:
> That is exactly what the http://llvm.cs.uiuc.edu/docs/ directory is: a
> mirror of the docs directory in CVS. It's autoupdated on every
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared(firstuse this function)
>From: "Reid Spencer" <reid at x10sys.com>
>Date: Thu, 15 Jul 2004 18:33:30 -0400
>
>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
2004 Jul 15
0
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 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
2004 Jul 15
0
[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
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)
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.
2004 Jul 15
2
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (firstuse this function)
On Thu, 15 Jul 2004 18:19:11 -0500 (CDT)
Chris Lattner <sabre at nondot.org> wrote:
> This has no impact on the users at all... it has an impact on the
> maintainers of the LLVM .bc file reader. :) The LLVM BC file reader has
> to have compatibility code to support loading of all released LLVM
> bytecode formats (1.0, 1.1, 1.2, etc).
Good point.
> There is always a
2011 Jun 14
0
klibc 1.5.23 release
This release features a dash sync to latest dash git (We continue in the
tradition of providing the freshest dash), porter fixes for arm Debian and
ppc64 Ubuntu. To the utils got added a minimal mv, so that /run initramfs
content can be moved to the real rootfs.
The shortlog is dominated by dash commits, plus usual minimal fixes.
git repository:
git://git.kernel.org/pub/scm/libs/klibc/klibc.git
2011 Dec 22
1
[Bug 44061] New: dri/nouveau: Build error with clang
https://bugs.freedesktop.org/show_bug.cgi?id=44061
Bug #: 44061
Summary: dri/nouveau: Build error with clang
Classification: Unclassified
Product: Mesa
Version: git
Platform: All
URL: http://lists.freedesktop.org/archives/mesa-dev/2011-No
vember/014310.html
OS/Version: Linux (All)
2004 Jul 14
1
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (first use this function)
Hi
By manipulating a #define for G++ I've managed to compile int64_t type with
ostream.
Now, I'm stopped by some to me unknown constants:
-----------------------------------
Compiling Constants.cpp
Constants.cpp: In static member function `static bool
llvm::ConstantSInt::isValueValidForType(const llvm::Type*, long long
int)':
Constants.cpp:368: error: `INT8_MAX' undeclared
2017 Jan 06
0
Wine release 2.0-rc4
The Wine development release 2.0-rc4 is now available.
What's new in this release (see below for details):
- Bug fixes only, we are in code freeze.
The source is available from the following locations:
http://dl.winehq.org/wine/source/2.0/wine-2.0-rc4.tar.bz2
http://mirrors.ibiblio.org/wine/source/2.0/wine-2.0-rc4.tar.bz2
Binary packages for various distributions will be available
2013 Jan 08
0
[PATCH] avoid undefined behavior in fmt_scaled()
fmt_scaled() computes the absolute value of its argument, and returns an
error if the result is still negative (i.e., when the value is LLONG_MIN).
However, taking the negative of LLONG_MIN is undefined behavior in C, and
some compilers (e.g., gcc-4.7.2) will optimize away the 'abval < 0' check
as being always false (since it can only be true with undefined behavior).
The patch
2004 Jul 27
1
[LLVMdev] ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (firstuse this function)
Hi John,
Please see below, too
>From: John Criswell <criswell at cs.uiuc.edu>
>Date: Tue, 27 Jul 2004 14:57:02 -0500
>
>Henrik Bach wrote:
>>Hi,
>
>Please see below.
>
>>
>>I get this error:
>>------------------
>>ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function)
>>ToolRunner.cpp:396: error: (Each
2004 Jul 27
1
[LLVMdev] ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (firstuse this function)
Hi again
Does cygwin support shared libraries. And if not, how did you port llvm on
this issue?
/Henrik
>From: "Henrik Bach" <henrik_bach_llvm at hotmail.com>
>Date: Tue, 27 Jul 2004 00:41:53 +0200
>
>Hi,
>
>I get this error:
>------------------
>ToolRunner.cpp:396: error: `SHLIBEXT' undeclared (first use this function)
>ToolRunner.cpp:396: