similar to: [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) >The file you need to modify is here: >llvm/include/Support/DataTypes.h.in > >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

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

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)

> > Okay, it's just not immediately undefined behaviour. The C model has more > issues because of the problem with how "trap representation" is defined > (which precludes trap representations for unsigned char, two's complement > signed char, etc.). This interpretation is further stressed because C only explicitly ascribes > undefined behaviour to trap

http://bugzilla.mindrot.org/show_bug.cgi?id=1104 Summary: Compile error "ldLL" not declared in strtonum.c under Tru64 Unix 4.0f Product: Portable OpenSSH Version: 4.2p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: critical Priority: P2 Component: Build system

Hi, beta4 built under RHEL4, RHEL5 and RHEL6 (the latter being the public beta). beta5 now builds only for RHEL5, the other two fail with: strnum.c: In function `str_to_llong': strnum.c:139: error: `LLONG_MIN' undeclared (first use in this function) strnum.c:139: error: (Each undeclared identifier is reported only once strnum.c:139: error: for each function it appears in.) Thanks! --

Kevin André wrote: > For my master's thesis, I am trying to cross compile programs for the > PSP (PlayStation Portable) with LLVM and llvm-gcc. > > This is what I do: > > (1) compile a program and the libraries it uses (libpng etc.) with llvm-gcc > (2) link the bitcode files with llvm-ld into one file > (3) run "llc -march=c" on the result > (4) compile

Hi All: This series introduces API for reporing IOVA range. This is a must for userspace to work correclty: - for the process that uses vhost-vDPA directly to properly allocate IOVA - for VM(qemu), when vIOMMU is not enabled, fail early if GPA is out of range - for VM(qemu), when vIOMMU is enabled, determine a valid guest address width Please review. Changes from V1: - do not mandate

For my master's thesis, I am trying to cross compile programs for the PSP (PlayStation Portable) with LLVM and llvm-gcc. This is what I do: (1) compile a program and the libraries it uses (libpng etc.) with llvm-gcc (2) link the bitcode files with llvm-ld into one file (3) run "llc -march=c" on the result (4) compile the resulting C source with the PSP toolchain It seems to work

If we compare the "common" subdirectory between nbdkit @ 6b4178d0fdfe ("ci: Temporarily disable perl in MacOS", 2023-02-27) and libnbd @ d05cd8f384a7 ("Version 1.15.11.", 2023-02-28), we find differences. We can categorize these differences along two (orthogonal) axes: - Intentional or unintentional. Intentional differences are for example when one of the libnbd

FWIW, the talks linked by Mehdi really do talk about these things and why I don't think the really are the correct trade-off. Even if you imagine an unsigned type that doesn't allow wrapping, I think this is a really bad type. The problem is that you have made the most common value of the type (zero in every study I'm aware of) be a boundary condition. Today, it wraps to a huge value

I've had trouble getting a definitive answer to this one, so please forgive me for asking here. When converting between integer and float audio samples, what is the preferred scale factor? For example, if you were converting to signed 8-bit, the possible range is -128 to 127. Do you map float -1.0 to -127 or -128? Brendan

If there is no free space, the free space allocator will try to get space from the block group with the degenerated profile. For example, if there is no free space in the RAID1 block groups, the allocator will try to allocate space from the DUP block groups. And besides that, the space reservation has the similar behaviour: if there is no enough space in the space cache to reserve, it will reserve

Hi all, This patch set adds batched discard support to ocfs2. Please check. Thanks. Regards, Tao

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

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

>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

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/

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

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 >