[Patch, fortran] Fix temporary allocation for class assignment.

2012-01-14 Thread Paul Richard Thomas
Dear All, As previously advertised, the attached patch fixes the problem with using an index array in the final assignment in subroutine qsort in class_array_3.f03. The failure occurred because the temporary array was assigned zero size, since the declared type is abstract. More generally, even

[PATCH] libffi fixes for m68k

2012-01-14 Thread Andreas Schwab
The only way to detect compiling for a plain 68000 is the absense of other defines since __mc68000__ is always defined. Also, gcc defines __HAVE_68881__, not __MC68881__. The latter fixes failures of all tests involving floating point return values. Tested on m68k-linux. Andreas. 2012-01-14 A

Re: [PATCH] libada: fix multilib bug

2012-01-14 Thread Arnaud Charlet
> s-oscons-tmplt.i must be compiled with the right MULTIFLAGS. Tested on > powerpc-linux. > > Andreas. > > 2012-01-14 Andreas Schwab > > * gcc-interface/Makefile.in (OSCONS_EXTRACT): Add $(GNATLIBCFLAGS). OK > diff --git a/gcc/ada/gcc-interface/Makefile.in > b/gcc/ada/gcc-interface/Ma

Re: [PATCH] Fix g++.dg/cpp0x/constexpr-rom.C failure

2012-01-14 Thread Andreas Schwab
Thanks, I hadn't discovered this yet. Andreas. 2012-01-14 Andreas Schwab * g++.dg/cpp0x/constexpr-rom.C: Add -G0 where applicable. diff --git a/gcc/testsuite/g++.dg/cpp0x/constexpr-rom.C b/gcc/testsuite/g++.dg/cpp0x/constexpr-rom.C index aa9ff5d..636f0e7 100644 --- a/gcc/testsuite/g+

Re: [PATCH] Fix g++.dg/cpp0x/constexpr-rom.C failure

2012-01-14 Thread Jakub Jelinek
On Sat, Jan 14, 2012 at 08:57:00PM +0100, Andreas Schwab wrote: > Fix spurious failure by disabling use of sdata. Tested on > powerpc-linux. Please use dg-additional-options instead. > 2012-01-14 Andreas Schwab > > * g++.dg/cpp0x/constexpr-rom.C: Add -G0 where applicable. > > diff --gi

[PATCH] Fix g++.dg/cpp0x/constexpr-rom.C failure

2012-01-14 Thread Andreas Schwab
Fix spurious failure by disabling use of sdata. Tested on powerpc-linux. Andreas. 2012-01-14 Andreas Schwab * g++.dg/cpp0x/constexpr-rom.C: Add -G0 where applicable. diff --git a/gcc/testsuite/g++.dg/cpp0x/constexpr-rom.C b/gcc/testsuite/g++.dg/cpp0x/constexpr-rom.C index aa9ff5d..5

[PATCH] libada: fix multilib bug

2012-01-14 Thread Andreas Schwab
s-oscons-tmplt.i must be compiled with the right MULTIFLAGS. Tested on powerpc-linux. Andreas. 2012-01-14 Andreas Schwab * gcc-interface/Makefile.in (OSCONS_EXTRACT): Add $(GNATLIBCFLAGS). diff --git a/gcc/ada/gcc-interface/Makefile.in b/gcc/ada/gcc-interface/Makefile.in index 6a7da

Re: [PATCH, AVR] Fix PR target/50925, use hard_frame_pointer_rtx

2012-01-14 Thread Denis Chertykov
2012/1/14 Denis Chertykov : > 2012/1/13 Georg-Johann Lay : >> Denis Chertykov wrote: >> >>> Committed >>> >>> Denis >> >> >> Consider code prom PR51374 >> >> void __vector_18 (void) >> { >>    extern char slot; >>    unsigned char status = (*(volatile unsigned char*) 0x2B); >>    unsigned char data

[v3] doxygen comments for reverse_iterator

2012-01-14 Thread Jonathan Wakely
2012-01-14 Jonathan Wakely * include/bits/stl_iterator.h (reverse_iterator): Doxygen comments. Tested x86_64-linux, committed to trunk. --- a/libstdc++-v3/include/bits/stl_iterator.h +++ b/libstdc++-v3/include/bits/stl_iterator.h @@ -1,7 +1,7 @@ // Iterators -*- C++ -*- // Copyrigh

Re: [C++ Patch] PR 51225

2012-01-14 Thread Paolo Carlini
Hi, On 01/13/2012 03:57 PM, Paolo Carlini wrote: Anyway, the reason we are not tsubst-ing such trees - eg, a CAST_EXPR on a single element TREE_LIST as argument, with error_mark_node as value - is that potential_constant_expression is false in fold_non_dependent_expr_sfinae, thus tsubst_copy_and

Re: [Patch, Fortran] PR 51800 - Fix -finit-local-zero with automatic arrays and -fno-automatic

2012-01-14 Thread Paul Richard Thomas
Dear Tobias, > Build and regtested on x86-64-linux. > OK for the trunk? That's OK for trunk - thanks! Paul

Re: [Patch, Fortran] PR51816 - fix USE of intrinsic operators

2012-01-14 Thread Paul Richard Thomas
Dear Tobias, > This patch fixes two issues related to intrinsic operators: > > a) No error for nonexisting operators: >USE m, operator(*) > > > b) An bogus error if one tried to use-associate the same operator multiple > times: > USE m, operator(+), operator(+) > > Those are old issues. New i