similar to: "make check" fails on lapack.R and stats-Ex.R

Hello, I experienced a compiler error when I tried to compile the latest version of R i.e. R4.0.2 making iosupport.d from iosupport.c making lapack.d from lapack.c making list.d from list.c making localecharset.d from localecharset.c grep.c(74): catastrophic error: cannot open source file "pcre2.h" # include<pcre2.h> (The pcre2.h header file is actually present!) I used the

I have access to a cluster on which I have been supplied with R 3.1.0 which appears to have been built using the intel compiler tools. The following minimal Fortran file: subroutine truth(lind) logical lind lind = .TRUE. end Compiles thusly: arcadia> R CMD SHLIB truth.f ifort -fpic -O3 -xHOST -axCORE-AVX-I -fp-model precise -c truth.f -o truth.o ifort: command

Full_Name: Mike Pacey Version: 2.6.0 OS: SuSe Linux 9.3 x86_64 Submission from: (NULL) (194.80.32.10) A "vanilla" version of R configures and compiles without a problem on my system. Switching to using the PGI compiler configures correctly (see the values at the bottom fo thismessage), but compilation aborts with: pgcc -I../../src/extra/zlib -I../../src/extra/bzip2

Whilst bored I purchased HalfLife for Windows, having read people mention on Slashdot that it runs on Wine. I run Debian (woody) on an AMD Athlon 1.4GHz machine with 1Gb RAM as my desktop. It currently has a Voodoo3 video card, though I have a dual head Radeon which I'm going to use once I get a monitor that is compatible (my current monitor has a very wavy display with that card). I

>>>>> Wim R Cardoen writes: > Hello, > I experienced a compiler error when I tried to compile the latest version > of R i.e. R4.0.2 > making iosupport.d from iosupport.c > making lapack.d from lapack.c > making list.d from list.c > making localecharset.d from localecharset.c > grep.c(74): catastrophic error: cannot open source file "pcre2.h" >

Hi folks, I'm attempting to compile and install 2.5.0, and "make check" is failing one of the earlier sanity tests. I'll append the relevant portion of the Rout.fail file below, but I've narrowed it down manually to a single command: > sessionInfo() R version 2.5.0 (2007-04-23) x86_64-unknown-linux-gnu locale:

System details: -------------- Sun Blade 1000, Solaris 8, Sun ONE Compiler Suite (rebranded Forte 7), R versions 1.6.0 and 1.6.2 - suspect others are affected, too Problem description: ------------------- Using the recommended env var setting from p.15 of the Admin Guide, the configure script fails the sgemm sunperf test, even though the sunperf libraries are available Not linking with

The Wine development release 1.5.3 is now available. What's new in this release (see below for details): - Support for graphics bounds tracking. - A number of fixes to the builtin Internet Explorer. - Support for displaying ARM code in the Wine debugger. - Various DirectMusic improvements. - Better namespace support in MSXML. - Various bug fixes. The source is available from the

Full_Name: Mike Pacey Version: 2.0, 1.9.x OS: Solaris 8 Submission from: (NULL) (194.80.32.8) Symptoms: -------------- It seems the latest version of the Sun Compiler Suite (Forte 9) has compatability issues with R's configure script. Starting with a fairly vanilla configure (I'm using 1.9.1 here, but I've replicated the problem on 1.9.0 and 2.0.0): % export CC=cc % export F77=f95

Full_Name: Mike Pacey Version: 2.5.1 OS: SUSE SE Linux 9.3 Submission from: (NULL) (194.80.32.10) Versions 2.5.0 and 2.5.1 currently fail "make check" on my system due to a silent failure in the call to Rd_db("base"): ----- > ### Name: Rdutils > ### Title: Rd Utilities > ### Aliases: Rd_db Rd_parse > ### Keywords: utilities documentation > > ### **

The Wine maintenance release 1.4.1 is now available. What's new in this release (see below for details): - Translation updates. - Various bug fixes. The source is available from the following locations: http://prdownloads.sourceforge.net/wine/wine-1.4.1.tar.bz2 http://mirrors.ibiblio.org/wine/source/1.4/wine-1.4.1.tar.bz2 Binary packages for various distributions will be available

Hello all, Thank everyone who participated in the (impromptu) round table discussion on Tuesday. For those who are interested, I share the summary of the discussion. Also, I share a short-term plan regarding this issue and relevant patches. *Fixing Miscompilations using Freeze* ----------------------------------- To reduce the cost of fixing miscompilations using freeze instruction, we need to

> It is important to note that this applies to trap representations and not to unspecified values. A structure or union never has a trap representation. Yes, nondeterministic bits would work for padding of struct/union, as described in (3) The third case is the value of struct/union padding. For the members of struct/union, it is allowed to have trap representation, so poison can be used.

It is UB when a poison is passed to certain operations that raise UB on poison, such as division by poison/dereferencing poison pointer/branching on poison condition/etc. Otherwise, poison is simply propagated, but it does not raise UB Copying poison bytes is okay: // Members are initialized to poison at object creation. p = alloca {i8, i32} // p[0], p[4~7] are poison q = alloca {i8, i32} // we

> > // Members are initialized to poison at object creation. >> p = alloca {i8, i32} // p[0], p[4~7] are poison >> p[0] is an i8, so it shouldn't be poison? > > My interpretation of standard is that reading uninitialized char can also yield trap representation. If uninitialized, char variable has indeterminate value, and C/C++ does not seem to forbid reading trap

> > 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