The site at code.google.com redirects to github now.
Applied.
Gerald
2017-02-19 Gerald Pfeifer
* doc/xml/manual/debug.xml: Adjust link to ThreadSanitizer.
Index: doc/xml/manual/debug.xml
===
--- doc/xml/manual/debug.xml
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 German team of translators. The file is available at:
http://translationproject.org/latest/gcc/de.po
(This file, 'gcc-7.1-b20170101.de.po', h
citeseer has been acting interestingly for a while, and now is
blocking clients based on geography (verified as blocking from
three different systems/networks in Austria and Germany on the
one hand¹, and working from the gcc.gnu.org host and another
one in North America on the other).
So, based
This has not been adopted by LEWG/LWG yet, but was submitted
as a proposed resolution for a new LWG issue; optional can't
current be compared to a T, and an optional can't be compared
to something non-T that is comparable to a T. This approach fixes
both of those problems, allowing optional's compa
On 18/02/17 20:48 +, Dinka Ranns wrote:
Comments addressed. Please find the new diff attached to this e-mail.
Changelog after review comments :
2017-02-18 Dinka Ranns
GNU ChangeLog rules say two spaces after the date and after your name.
C++17 GB50 resolution
* include/st
Hi Markus,
On Wed, 1 Feb 2017, Markus Trippelsdorf wrote:
> Some colors on e.g. https://gcc.gnu.org/gcc-7/changes.html are nearly
> unreadable. So what about the following patch?
>
> -.boldcyan{ font-weight:bold; color:cyan; }
> -.boldlime{ font-weight:bold; color:lime; }
> +.boldcyan
Ping!
this time with correct PR number: 79229.
On Tue, 7 Feb 2017 08:31:22 +0100
Andre Vehreschild wrote:
> Hi all,
>
> attached patch fixes the issue of 79229 (which is not a regression).
> The issue was that the code generating the checking was expecting a
> pointer type, but got an indirect
On 02/19/2017 08:42 AM, Andre Vehreschild wrote:
Ping!
this time with correct PR number: 79229.
On Tue, 7 Feb 2017 08:31:22 +0100
Andre Vehreschild wrote:
Hi all,
attached patch fixes the issue of 79229 (which is not a regression).
The issue was that the code generating the checking was exp
On Fri, Feb 17, 2017 at 5:59 PM, Uros Bizjak wrote:
> On Fri, Feb 17, 2017 at 5:30 PM, Jakub Jelinek wrote:
>> On Sun, May 29, 2016 at 11:10:15PM +0200, Uros Bizjak wrote:
>>> As explained in PR71245, comment #3 [1], it is better to use offset -4
>>> to a %esp to implement a non-SSE memory fence
Hi Everybody,
With Jerry's OK for a commit to trunk, committed as revision 245580.
I will wait a few weeks before a commit to 6-branch.
Cheers
Paul
On 11 February 2017 at 13:24, Paul Richard Thomas
wrote:
> Ping!
>
> On 8 February 2017 at 16:00, Paul Richard Thomas
> wrote:
>> Dear All,
>>
Hi Jerry, hi all,
thanks for the review. Committed as r245581.
Regards,
Andre
On Sun, 19 Feb 2017 08:58:46 -0800
Jerry DeLisle wrote:
> On 02/19/2017 08:42 AM, Andre Vehreschild wrote:
> > Ping!
> >
> > this time with correct PR number: 79229.
> >
> > On Tue, 7 Feb 2017 08:31:22 +0100
Hi Jerry,
Committed as revision 245582.
Thanks for the review.
Paul
On 16 February 2017 at 00:37, Jerry DeLisle wrote:
> On 02/15/2017 10:01 AM, Paul Richard Thomas wrote:
>> Dear All,
>>
>> This patch is straightforward, verging on 'obvious'.
>>
>> Bootstraps and regtests on FC23/x86_64 - OK
On 02/17/2017 09:53 PM, Jason Merrill wrote:
On Thu, Feb 16, 2017 at 6:13 PM, Martin Sebor wrote:
On 02/16/2017 12:49 PM, Jason Merrill wrote:
On Thu, Feb 16, 2017 at 11:33 AM, Jakub Jelinek wrote:
PR c++/79502
* pt.c (apply_late_template_attributes): If there are
n
On Wed, 15 Feb 2017, Michael Eager wrote:
> The DWARF Debugging Information Format Standards Committee is pleased
> to announce the availability of Version 5 of the DWARF Debugging Format
> Standard.
This patch, which I just applied, updates the GCC 7 release notes
accordingly.
(Now it's only
That was quite a bit; thanks for doing that, Jakub!
In the patch below I try to streamline language a bit, document options
being implied by -Os (in addition to -O2 or higher), fix grammar in a few
places, and change a textual link to being a real one.
I have _not_ applied this yet, and would a
In the old inheriting constructor scheme, copy constructors were not
inherited. In the new scheme we needed a rule to get a similar
effect; I proposed that an inherited constructor should not be viable
if it has a single parameter of a type reference-related to the
derived type. Richard Smith pro
We were treating a compound literal type defined in the initializer
for a static data member as though it were a member of the class.
Fixed by ignoring classes when defining a type from within an
expression.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 23c08aed737764678bbe1af31ddaa16b2d0a
DECL_TEMPLATE_RESULT doesn't work on a non-template, so let's use
STRIP_TEMPLATE instead.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 9f99104a12b72006253c0ce5f0b046ada82eb354
Author: Jason Merrill
Date: Sun Feb 19 14:01:51 2017 -0800
PR c++/79500 - ICE with non-template d
We have code in unify to handle the implicit indirection through a
reference, but it couldn't handle when that indirection was wrapped in
an EXPR_PACK_EXPANSION.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 75e6ade977ea2d229d5ccd4fdaaf812c634c4d41
Author: Jason Merrill
Date: Sun Feb 19
It was pointed out that suggesting noexcept as an alternative to
throw(type) doesn't make much sense, since throw(type) would imply
noexcept(false), which is the default. So let's just remove the
suggestion.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 41d5a30463d1f62dfb64ec953b662e1eda5
In the parser, declares_class_or_enum is set to 1 for an elaborated
type-specifier, or 2 for a class or enum definition. We only want to
complain about a type definition in the latter case.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 8b366b7f80be1f160bd31501aa436e4d300cd753
Author: Jaso
type_dependent_init_p was overlooking the possibility of a CONSTRUCTOR
with a dependent type, which we can get from T{}.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 060f95851e7f6d6737937b786c0a6b29cda3c454
Author: Jason Merrill
Date: Sun Feb 19 15:40:39 2017 -0800
PR c++/
build_base_path knows that it should limit what it tries to do within
a template, but that handling wasn't being used within an NSDMI, only
within a template function.
Tested x86_64-pc-linux-gnu, applying to trunk.
commit 7a11cba1268aa91df1bc253c43deb2dcbfd5b091
Author: Jason Merrill
Date: Sun
When looking for parameter packs mentioned within an expression, we
were wrongly walking into the type of a TEMPLATE_DECL mentioned in the
expression. We're only interested in packs in the type of a template
template-parameter, not other kinds of template.
Tested x86_64-pc-linux-gnu, applying to
On 02/13/2017 11:14 PM, Sandra Loosemore wrote:
2017-02-13 Sandra Loosemore
gcc/
* doc/invoke.texi (ARC Options): Copy-edit to fix punctuation,
markup, and similar issues. Remove @opindex entries for things
that aren't options.
Target maintainers, any comme
25 matches
Mail list logo
