The patch is a bit large since it does the baseline_symbols regeneration
and other new-version api-dance.
Hence attached gzipped.
Tested on Linux x86-64.
2015-04-13 Ville Voutilainen ville.voutilai...@gmail.com
Add support for std::uncaught_exceptions.
* acinclude.m4: Bump
On Sat, Apr 11, 2015 at 5:48 AM, Gerald Pfeifer ger...@pfeifer.com wrote:
Hi Terry,
I went ahead and committed some small changes to the description of
-masm-syntax-unified. Let me know if you disagree or would like to
see further changes.
Gerald
Thanks for the improvement. I am totally
PR libstdc++/62259
PR libstdc++/65147
* include/std/atomic (atomicT): Increase alignment for types with
the same size as one of the integral types.
* testsuite/29_atomics/atomic/60695.cc: Adjust dg-error line number.
*
Note that before the fixes for PR64909 the epilogue/prologue loops had very
large costs associated due to a bug in the cost model implementation. After
the fix their cost is reasonable but the cost of the extra jumps is way
under-accounted for due to the numbers for cond_taken_branch_cost and
On 04/02/2015 11:59 PM, Yangfei (Felix) wrote:
Patch ping: https://gcc.gnu.org/ml/gcc-patches/2014-11/msg01148.html
This patch needs documentation for the new attributes and pragmas before it
can be committed. (Since this is a new feature I think it has to wait until
stage 1,
too, but
On Wed, Mar 18, 2015 at 12:12:17PM +0100, Richard Biener wrote:
On Wed, Mar 18, 2015 at 5:22 AM, Alan Modra amo...@gmail.com wrote:
On Tue, Mar 17, 2015 at 01:28:41PM -0600, Jeff Law wrote:
On 03/14/2015 07:02 AM, Alan Modra wrote:
PR target/65408
PR target/58744
PR
On Thu, 5 Feb 2015, Matthew Fortune wrote:
Thanks Catherine. Good call to remove the markup while reviewing. I've
done one more pass on this to have the same phrasing used where similar
points are being made. I also added a comment about link compatibility
for FP64. Updated text is at the
[ Tobias, your bur...@net-b.de account just bounced with mailbox full! ]
On Tue, 18 Feb 2014, Tobias Burnus wrote:
is the wording okay - and/or do you have further suggestions?
Here are some suggestions on top of the existing text.
Remove a comma and break a long sentence in the SIMD section.
On Mon, 14 Jan 2013, Dave Johansen wrote:
+GCC plugin support is available in GCC version 4.5.0 and
+later.
What's the value of documenting the availability of an unstable API in
older versions
of GCC? Mind this documentation is version specific.
Richard.
My point wasn't to encourage
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'cpplib' has been submitted
by the Serbian team of translators. The file is available at:
http://translationproject.org/latest/cpplib/sr.po
(This file,
cpplib-5.1-b20150208.sr.po.gz
Description: Binary data
The Translation Project robot, in the
name of your translation coordinator.
coordina...@translationproject.org
On Wed, 13 Mar 2013, Benjamin De Kosnik wrote:
Hey! Here is the first pass at the 4.8 porting documentation.
Lovely, thank you, I know this really has proven useful.
And with some unfortunate of delay, some updates from my side:
- Use run-time performance (instead of runtime performance which
Earlier this year I realized Maxim was completely missing, so here
we go.
Applied.
2015-04-12 Gerald Pfeifer ger...@pfeifer.com
* doc/contrib.texi (Contributors): Add Maxim Kuvyrkov.
Index: doc/contrib.texi
===
---
The attached patch is a back port of the change from
https://gcc.gnu.org/viewcvs/gcc?view=revisionrevision=211067 for
gcc-4_9-branch. Bootstrap and regression tested on
x86_64-apple-darwin14 with Xcode 6.3. Okay for gcc-4_9-branch?
Jack
2015-04-12 Jack Howarth
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Swedish team of translators. The file is available at:
http://translationproject.org/latest/gcc/sv.po
(This file, 'gcc-5.1-b20150208.sv.po',
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the Finnish team of translators. The file is available at:
http://translationproject.org/latest/gcc/fi.po
(This file, 'gcc-5.1-b20150208.fi.po',
On Sun, 12 Apr 2015, Michael Witten wrote:
Well, now! What a pleasant surprise! I was looking for a reason
to crack open a beer, and this shall do nicely.
:-)
Say, how did you end up coming across this patch after nearly 4 years?
I keep things that might require attention in case nobody
OK.
Jason
Hi!
On the following testcase, ICF assumes OBJ_TYPE_REF_OBJECT must be a
SSA_NAME, but that is not the case in the testcase, where it is
ADDR_EXPR of MEM_REF instead.
Fixed thusly, bootstrapped/regtested on x86_64-linux and i686-linux, ok for
trunk?
2015-04-12 Jakub Jelinek ja...@redhat.com
Hi!
Here is an attempt to adjust gcc_release for 5+ versioning scheme.
The second hunk hopefully will use the right branch version, the first hunk
(to be tested when -f will be invoked) should bump automatically BASE-VER
(e.g. from 5.0.1 to 5.1.0).
I'd think we should perhaps also change all the
Hi Jakub,
On Fri, 11 Jul 2014, Jakub Jelinek wrote:
So like this? Also have fixed one omitted line in c-parser.c,
this patch bootstrapped/regtested fine:
just in time for GCC 5.1 RC1 :-) a small update on top of yours.
Committed.
Gerald
2015-04-12 Gerald Pfeifer ger...@pfeifer.com
On April 12, 2015 9:08:34 PM GMT+02:00, Jakub Jelinek ja...@redhat.com wrote:
Hi!
On the following testcase, ICF assumes OBJ_TYPE_REF_OBJECT must be a
SSA_NAME, but that is not the case in the testcase, where it is
ADDR_EXPR of MEM_REF instead.
Fixed thusly, bootstrapped/regtested on
Small Fortran update for https://gcc.gnu.org/gcc-5/changes.html :
The main issue with coarray locking has been solved :-)
Hence, I committed the patch as obvious.
Tobias
PS: Gerald: Regarding the approval for gcc-5/changes.html: Mention that
C FE can be build as libcc1.so: I withdraw/drew the
...a Honza/Gerald co-production. :-) Applied.
Jakub, is this (and another one I should have in the next few
days) okay to backport even after RC1?
Gerald
2015-04-12 Jan Hubicka hubi...@ucw.cz
Gerald Pfeifer ger...@pfeifer.com
* doc/contrib.texi (Contributors): Add
Hi all,
The attached patch fixes this bug. It also eliminates non-freed memory whenever
a format error occurs. Particular important when the user has use IOSTAT and
generate_error does not exit, but returns to continue program execution.
Regression tested on x86-64 and tested with
25 matches
Mail list logo
