This documentation patch only has boring formatting changes.
I spotted some over-long lines in the Option Summary section in the PDF
version of the GCC manual. While I was fixing that up, I saw that
several places were also inconsistent about whether to use one space or
two to separate option
On Tue, Jan 3, 2017 at 6:17 AM, Jonathan Wakely wrote:
> On 01/01/17 04:17 -0800, Tim Shen via libstdc++ wrote:
>>
>> +#define _VARIANT_RELATION_FUNCTION_TEMPLATE(__op, __name) \
>> + template \
>> +constexpr bool operator __op(const variant<_Types...>& __lhs, \
>> +
On 12/23/2016 02:25 PM, Martin Sebor wrote:
Bug 78703 points out that the decimal point character in floating
directives can be longer than just one byte (in locales where the
decimal point is a multibyte character). The decimal point can
result in anywhere between 1 and MB_LEN_MAX bytes. This
On 01/08/2017 02:04 PM, Martin Sebor wrote:
On 01/06/2017 09:45 AM, Jeff Law wrote:
On 01/05/2017 08:52 PM, Martin Sebor wrote:
So Richi asked for removal of the VR_ANTI_RANGE handling, which would
imply removal of operand_signed_p.
What are the implications if we do that?
I just got back to
I've checked in this patch to fix another long-standing (but easy)
documentation PR.
-Sandra
2017-01-08 Sandra Loosemore
PR middle-end/17660
gcc/
* extend.texi (Common Variable Attributes): Add xref to GCC
Internals manual to explain mode attribute keywords.
Index: gcc/doc/extend.texi
Returning to a patch I first posted about a month ago: the conclusion
seemed to be that -pthread needed to be documented with both the linker
and preprocessor options. Now that I've gotten the existing cpp options
documentation at least somewhat cleaned up of other cruft :-) I've
checked in th
PR tree-optimization/78913 - Probably misleading error reported by
-Wformat-length
PR middle-end/77708 - -Wformat-length %s warns for snprintf
gcc/c-family/ChangeLog:
PR tree-optimization/78913
PR middle-end/77708
* c.opt (-Wformat-truncation): New option.
gcc/testsuite/ChangeLog:
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 Danish team of translators. The file is available at:
http://translationproject.org/latest/gcc/da.po
(This file, 'gcc-7.1-b20170101.da.po', h
On 01/06/2017 09:45 AM, Jeff Law wrote:
On 01/05/2017 08:52 PM, Martin Sebor wrote:
So Richi asked for removal of the VR_ANTI_RANGE handling, which would
imply removal of operand_signed_p.
What are the implications if we do that?
I just got back to this yesterday. The implications of the rem
Committed.
Gerald
2017-01-08 Gerald Pfeifer
* download_ecj: Remove.
Index: download_ecj
===
--- download_ecj(revision 244208)
+++ download_ecj(nonexistent)
@@ -1,25 +0,0 @@
-#! /bin/sh
-
-#
-# Download t
> The patch also tightens scan-assembler patterns in a couple of pr78904
> testcases.
This caused https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79026.
TIA
Dominique
> r244027 reverts r244011. Sorry for the breakage. It seems to affect
> all i686 as well in addition to power, maybe all 32-bit hosts.
For the record, I see the following failures with an instrumented r244026 (as
in pr78672)
FAIL: gfortran.dg/char_length_20.f90 -O* execution test
FAIL: gfortr
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-7.1-b20170101.sv.po',
Hi,
this patch fixes hitrate of indirect call predictor according to Martin's
measurements.
Boostrapped/regtested x86_64-linux, comitted.
Honza
PR middle-end/77484
* predict.def (PRED_INDIR_CALL): Set to 86.
Index: predict.def
=
14 matches
Mail list logo
