Test on secondary gcc platform i686-w64-mingw32:
...
GMP: include 5.0.5, lib 5.0.5
MPFR: include 3.1.1, lib 3.1.1
MPC: include 1.0.0rc1, lib 1.0.0rc1
C compiler: i686-w64-mingw32-gcc
GCC: yes
GCC version: 4.7.2
PASS: tget_version.exe
===
All 64 tests passed
===
Rega
Test on x86_64-apple-darwin10
GMP: include 5.0.4, lib 5.0.4
MPFR: include 3.1.1, lib 3.1.1
MPC: include 1.0.0rc1, lib 1.0.0rc1
C compiler: gcc
GCC: yes
GCC version: 4.8.0
PASS: tget_version
===
All 64 tests passed
===
Dominique
On 07.07.12 17:13, Andreas Enge wrote:
We are pleased to announce the immediate availability of the first release
candidate for GNU MPC 1.0 at
http://www.multiprecision.org/mpc/download/mpc-1.0.0rc1.tar.gz
sha1sum 9acc8a54ba4ecd0ccf172c0d07fcc218220e79a3
Reports on successful installatio
On 2012-07-01, at 12:53 PM, Vincent Rivière wrote:
> On 01/07/2012 16:16, t-rexky wrote:
>> I discovered that if I rebuild stage 3 with BOOT_CFLAGS="-g -O0", the
>> warnings in stage 3 compiler all disappear!
>
> This is extremely wierd!
>
> So it looks like something is affected by the optimiza
Test on x86_64-w64-mingw32 :
GMP: include 5.0.5, lib 5.0.5
MPFR: include 3.1.1, lib 3.1.1
MPC: include 1.0.0rc1, lib 1.0.0rc1
C compiler: i686-w64-mingw32-gcc -m64
GCC: yes
GCC version: 4.7.2
PASS: tget_version.exe
===
All 64 tests passed
===
On Sat, Jul 7, 2012 at
My C++ application which uses Qt and libsigc++ libraries is stable if
all 3 components are compiled with GCC 4.4.7
If my app is compiled with GCC 4.7.1 it crashes in random time and
place inside Qt library as detected by GDB.
I tried to run app with Valgrind, but didn't have crash yet.
How can I fi
On 8 July 2012 18:43, wbrana wrote:
> My C++ application which uses Qt and libsigc++ libraries is stable if
> all 3 components are compiled with GCC 4.4.7
> If my app is compiled with GCC 4.7.1 it crashes in random time and
> place inside Qt library as detected by GDB.
> I tried to run app with Val
On 08.07.12 12:32, Andreas Tobler wrote:
On 07.07.12 17:13, Andreas Enge wrote:
We are pleased to announce the immediate availability of the first release
candidate for GNU MPC 1.0 at
http://www.multiprecision.org/mpc/download/mpc-1.0.0rc1.tar.gz
sha1sum 9acc8a54ba4ecd0ccf172c0d07fcc21
When a peephole is recognized, the first insn in the group is replaced by a
pseudo insn that contains all the referenced operands in the TEMPLATE and sets
an INSN_CODE to indicate which peephole matched.
This is all well and good, except that if the peephole involves a CALL_INSN,
final_scan_ins
On Sun, Jul 8, 2012 at 2:23 PM, Alan Lehotsky wrote:
> When a peephole is recognized, the first insn in the group is replaced by a
> pseudo insn that contains all the referenced operands in the TEMPLATE and
> sets an INSN_CODE to indicate which peephole matched.
>
> This is all well and good, ex
I'm certain there are better ways; can you be more specific though?
Or are you just talking about defining a sibcall_epilogue pattern?
On Jul 8, 2012, at 5:26 PM, Andrew Pinski wrote:
> On Sun, Jul 8, 2012 at 2:23 PM, Alan Lehotsky wrote:
>> When a peephole is recognized, the first insn in the
Snapshot gcc-4.8-20120708 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20120708/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
- Original Message -
From: "Andreas Enge"
To: ;
Sent: Sunday, July 08, 2012 1:13 AM
Subject: [Mpc-discuss] GNU MPC 1.0 release candidate
We are pleased to announce the immediate availability of the first release
candidate for GNU MPC 1.0 at
http://www.multiprecision.org/mpc/downl
13 matches
Mail list logo
