Manuel López-Ibáñez wrote:
> The message for the following error:
>
> enum e { E3 = 1 / 0 };
>
> is in C: error: enumerator value for 'E3' not integer constant
> and in C++: error: enumerator value for 'E3' is not an integer constant
>
> Is there someone against fixing this? What would be the p
When GCC uses MPFR in the middle-end, it sets the precision of the MPFR
variables used for intermediate calculations to the "p" field of the
target float format. We need the precision of the MPFR variables to be
exactly the same number of bits as the target float format so we can
determine when th
On Tue, 21 Nov 2006, Diego Novillo wrote:
> With the exception of DLV and SPEC2000, we could probably add most of
> them to the check-compile testsuite. I don't know if Gerald would be
> able to allow DLV to be included.
I am, unfortunately, not able to make it completely public but if further
Richard,
Somewhere, in a mail lost in my large e-mail clash with my ISP
(verizon), you said that gfortran couldn't profit from the pow(x, 1./3.)
-> cbrt(x) conversion because gfortran didn't "know" of cbrt.
Could you be more explicit about this - I'd like to repair this
deficiency, if at all
This patch updates the GCC prerequisite documenation and error message
code in gcc 4.2 to reflect using mpfr-2.2.1.
The 4.2 branch never actually forces any particular version of mpfr, it
merely notes when you have a "buggy" version and tells you about it when
you configure GCC.
If you're missin
This patch updates configure to require MPFR 2.2.1 as promised here:
http://gcc.gnu.org/ml/gcc/2006-12/msg00054.html
Tested on sparc-sun-solaris2.10 using mpfr-2.2.1, mpfr-2.2.0 and an older
mpfr included with gmp-4.1.4. Only 2.2.1 passed (as expected).
I'd like to give everyone enough time to u
Hi Kaveh,
On Thu, 16 Nov 2006, Kaveh R. GHAZI wrote:
> I'm wondering, can we can solve this with a better error message? That
> should tickle enough brain cells to hopefully lower the chance of someone
> being bit by this. Let me know your thoughts.
yes, this definitely looks like a very good a
On 01 December 2006 08:13, Eric Botcazou wrote:
>> I have built a static runtime library and i want the linker to access
>> it automatically without having to pass it explicitly.
>
> Wrong list, this one is for GCC development, not development with GCC.
So, the answer from this list is "add i
Hi Richie,
On Tue, 21 Nov 2006, Richard Guenther wrote:
> Public monitoring would be more useful. If you have working single-file
> testcases that you want be monitored for compile-time and memory-usage
> just contact me and I can add them to the daily tester
> (http://www.suse.de/~gcctest/c++
