>From 609cef6c863633711418c6b23401069062ac5df8 Mon Sep 17 00:00:00 2001
From: expnkx
Date: Wed, 14 Apr 2021 01:48:38 -0400
Subject: [PATCH] Fix freestanding cstdint which fails to detect
stdint.h [PR100057]
Configure script cannot find cstdint when we build in freestanding
environment since
>From 71e6b5bcf5564ecc59a96fdf2939537e4ccf0004 Mon Sep 17 00:00:00 2001
From: expnkx
Date: Wed, 14 Apr 2021 00:17:53 -0400
Subject: [PATCH] Fix build errors on several platforms.
[PR100057,PR100012,PR99499,PR99306]
[PATCH] libstdc++: Fix build errors with --disable-hosted-libstdcxx [PR100057]
In this testcase, the non-type template parameter has the type of a
lambda-expression. This makes no sense because a lambda in template context
is specified to be distinct between different specializations of the
template, even if the lambda is non-dependent, but here which specialization
we are
On Mon, Apr 12, 2021 at 6:20 PM Cui, Lili via Gcc-patches
wrote:
>
>
> Updated wwwdocs for Rocketlake [GCC11], thanks.
>
> [PATCH] Mention Rocketlake
> ---
> htdocs/gcc-11/changes.html | 4
> 1 file changed, 4 insertions(+)
>
> diff --git a/htdocs/gcc-11/changes.html
Hi,
On 2021/3/26 15:35, Xionghu Luo via Gcc-patches wrote:
>> Also we already have a sinking pass on RTL which even computes
>> a proper PRE on the reverse graph - -fgcse-sm aka store-motion.c.
>> I'm not sure whether this deals with non-stores but the
>> LCM machinery definitely can handle
On Tue, Apr 13, 2021 at 6:38 PM Uros Bizjak wrote:
>
> On Tue, Apr 13, 2021 at 12:18 PM Hongtao Liu wrote:
> >
> > Hi:
> > As described in PR, we introduced tigerlake string in driver-i386.c
> > by r9-8652 w/o support -march/tune=tigerlake which causes an error
> > when using
On 4/13/21 6:36 PM, Patrick Palka wrote:
In the testcase ref11.C below, during deduction for the call f(a),
uses_deducible_template_parms returns false for the dependent
specialization A because V is wrapped in an implicit INDIRECT_REF
(formed from template_parm_to_arg), and this causes
Here when we merged the specialization with the implicit instantiation
declaration, we wrongly kept the value of DECL_INITIALIZED_IN_CLASS_P from
the latter.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog:
PR c++/90674
* decl.c (duplicate_decls): Don't propagate
PR49951 complained about the debugger jumping back to the declaration of a
local variable when we run its destructor. That was fixed in 4.7, but broke
again in 4.8. PR58123 fixed an inconsistency in the behavior, but not the
jumping around. This patch addresses the issue by setting
In the testcase ref11.C below, during deduction for the call f(a),
uses_deducible_template_parms returns false for the dependent
specialization A because V is wrapped in an implicit INDIRECT_REF
(formed from template_parm_to_arg), and this causes unify_one_argument
to exit early, causing deduction
Hi!
On Fri, Apr 09, 2021 at 10:42:50AM -0400, Michael Meissner wrote:
> Since then the patch seems to have gone into a limbo state.
Patches I cannot immediately handle take time, and if they aren't
pinged, they can fall off the map. So a) ping your patches, once a week
for example; and b) write
The bug was fixed years ago. r11-8162 adds the test case to the test
suite.
https://gcc.gnu.org/g:af7128621e54f04b90589bb0c3e1ef271c239265
Martin
The issue has been fixed so r11-8161 just adds the test case:
https://gcc.gnu.org/g:8084ab15a3e300e3b2c537e56e0f3a1b00778aec
Martin
On Tue, 13 Apr 2021, Jason Merrill wrote:
> On 4/13/21 8:41 AM, Jason Merrill wrote:
> > On 4/12/21 6:24 PM, Patrick Palka wrote:
> > > On Mon, 12 Apr 2021, Jason Merrill wrote:
> > >
> > > > On 4/10/21 3:57 PM, Patrick Palka wrote:
> > > > > Here, in C++17 mode, we only pedwarn about the use of
On Linux/x86_64,
8913b2c2bcded39427ff27e6dfc276ae8555f6b8 is the first bad commit
commit 8913b2c2bcded39427ff27e6dfc276ae8555f6b8
Author: Patrick Palka
Date: Tue Apr 13 12:35:33 2021 -0400
c++: Reject alias CTAD in C++17 [PR99008]
caused
FAIL: g++.old-deja/g++.ns/crash3.C -std=c++17
We also need to check that the cv-qualifiers are the same.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog:
PR c++/100032
* pt.c (get_underlying_template): Compare TYPE_QUALS.
gcc/testsuite/ChangeLog:
PR c++/100032
*
On 4/13/21 8:41 AM, Jason Merrill wrote:
On 4/12/21 6:24 PM, Patrick Palka wrote:
On Mon, 12 Apr 2021, Jason Merrill wrote:
On 4/10/21 3:57 PM, Patrick Palka wrote:
Here, in C++17 mode, we only pedwarn about the use of alias CTAD and
then later ICE from alias_ctad_tweaks when attempting to
Hi!
This was fixed by r11-5866 aka PR96299 fix.
This just adds a testcase for it into the testsuite, tested
on x86_64-linux -m32/-m64, committed to trunk.
2021-04-13 Jakub Jelinek
PR c++/97121
* g++.dg/cpp2a/spaceship-err6.C: New test.
---
On Tue, 2021-04-13 at 14:21 -0400, David Malcolm via Gcc-patches wrote:
> On Tue, 2021-04-13 at 08:08 +0200, Jan Hubicka wrote:
> > Hi,
> > stepping through the streaming process it turns out to be funny
> > difference between gimple_has_body and node->has_gimple_body_p.
> > While the first tests
On Tue, 2021-04-13 at 08:08 +0200, Jan Hubicka wrote:
> Hi,
> stepping through the streaming process it turns out to be funny
> difference between gimple_has_body and node->has_gimple_body_p.
> While the first tests whether gimple body really exists in memory (by
> looking for
get_nsdmi instantiates default member initializers on demand. It tries to
push into the context of the class before doing so, so access checking works
properly, but since my patch for 90479 not for local classes. We should
only be doing this when any template parameters have arguments. But in
Hi!
On Fri, Apr 09, 2021 at 11:54:57AM -0500, will schmidt wrote:
> On Fri, 2021-04-09 at 10:42 -0400, Michael Meissner wrote:
> > * config/rs6000/rs6000.c (rs6000_emit_minmax): Add support for ISA
> > 3.1 IEEE 128-bit floating point xsmaxcqp and xsmincqp instructions.
>
> I don't see
On 4/13/21 10:07 AM, Jeff Law wrote:
On 4/8/2021 4:15 PM, Martin Sebor via Gcc-patches wrote:
The C front end ordinarily merges function type attributes upon
the redeclaration of a function but it doesn't do that for those
at local scope, unless the declaration refers to a built-in.
Because
libstdc++-v3/ChangeLog:
PR libstdc++/100060
* include/std/bit: Only include for
hosted build, use otherwise.
Tested powerpc64le-linux. Committed to trunk.
This needs to be backported to gcc-10 too.
commit 474cb5a0a404c5de7c1cd21aac8b1b7e7ce95d9b
Author: Jonathan
On 4/7/2021 5:46 PM, Martin Sebor via Gcc-patches wrote:
The attached patch fixes a couple of typos. Not sure they qualify
as regressions but it seems like a trivial fix worth making even
now. I'll go ahead and commit it as obvious if no-one objects.
Yea, this kind of diagnostic message
On 4/8/2021 4:15 PM, Martin Sebor via Gcc-patches wrote:
The C front end ordinarily merges function type attributes upon
the redeclaration of a function but it doesn't do that for those
at local scope, unless the declaration refers to a built-in.
Because the new -Warray-parameter warning
On 4/12/2021 11:45 AM, Victor Tong via Gcc-patches wrote:
Hello,
I'd like to ping this patch. It contains two new tree-opt patterns in match.pd.
[PATCH] tree-optimization: Optimize division followed by multiply [PR95176]
On 4/12/21 7:03 PM, H.J. Lu wrote:
On Mon, Apr 12, 2021 at 4:55 PM Martin Sebor wrote:
On 4/12/21 3:53 PM, H.J. Lu via Gcc-patches wrote:
On Mon, Apr 12, 2021 at 2:21 AM Richard Biener
wrote:
On Sat, Apr 10, 2021 at 5:11 PM H.J. Lu via Gcc-patches
wrote:
Add inline_ignore_target
On 13/04/21 16:37 +0100, Jonathan Wakely wrote:
On 13/04/21 16:19 +0100, Jonathan Wakely via Libstdc++ wrote:
Sorry for the slow reply ...
On Mon, 1 Feb 2021 at 22:59, Gerald Pfeifer wrote:
I noticed this section on "Backwards Compatibility" in the libstdc++
docs that talks about
- glibc
On Tue, 2021-04-13 at 10:52 +0100, Gaius Mulley wrote:
>
>
> Hello David and fellow GCC developers,
>
> [the proposed patches for GCC trunk are at the end of the email]
>
> I've been having way too much fun with your -fanalyzer code and
> here are four patches which give the analyzer the
> OK
Thanks. And it turns out that the limit on the size of accepted Ada files had
been already lowered earlier, namely when location ranges had been introduced.
Now we do not make use of location ranges in Ada, so we can recoup the loss.
Tested on x86-64/Linux, applied on the mainline, 10
On 12/04/2021 14:04, Srinath Parvathaneni via Gcc-patches wrote:
Hi,
The current CMSE support in the multilib build for "-march=armv8.1-m.main+mve
-mfloat-abi=hard -mfpu=auto"
is broken as specified in PR99939 and this patch fixes the issue.
Regression tested on arm-none-eabi and found no
Hi all,
This patch fixes PR99988 which shows us generating large (> 250)
sequences of back-to-back bti j instructions.
The fix is simply to avoid inserting bti j instructions at the target of
a jump table if we've already inserted one for a given label.
Testing:
* Bootstrapped and regtested on
Hi,
Martin Liška correctly observed that the newly added support for AMD
zenver3 in GCC 11 and 10.3 is not reflected in the changes.html files.
Would the following be OK?
Thanks,
Martin
diff --git a/htdocs/gcc-10/changes.html b/htdocs/gcc-10/changes.html
index d5166879..d9971ffb 100644
---
On 4/12/21 6:24 PM, Patrick Palka wrote:
On Mon, 12 Apr 2021, Jason Merrill wrote:
On 4/10/21 3:57 PM, Patrick Palka wrote:
Here, in C++17 mode, we only pedwarn about the use of alias CTAD and
then later ICE from alias_ctad_tweaks when attempting to add a
constraint to one of the guides.
This adds disambiguation of the access size vs. the decl size
in the pointer based vs. decl based disambiguator. We have
a TBAA based check like this already but that's fend off when
seeing alias-sets of zero or when -fno-strict-aliasing is in
effect. Also the perceived dynamic type could be
This avoids doing optimistic dominance queries involving
non-executable backedges when validating recorded predicated values
in VN because we have no way to force re-evaluating validity when
optimistically not executable edges become executable later.
Bootstrapped and tested on
Here we complained about referring to nm3 from the local class member
function because referring to the base class subobject involved taking the
variable's address. Let's shortcut this case to avoid that.
Tested x86_64-pc-linux-gnu, applying to trunk.
gcc/cp/ChangeLog:
PR c++/91933
This ICE was because when adjusting a column offset we could advance
into a linemap for a different file. We only checked the next line map
was not for a line further advanced in any file, forgetting that it
could be for an earlier line in a different file. The testcase needed
adjusting as
On Tue, Apr 13, 2021 at 12:18 PM Hongtao Liu wrote:
>
> Hi:
> As described in PR, we introduced tigerlake string in driver-i386.c
> by r9-8652 w/o support -march/tune=tigerlake which causes an error
> when using -march/tune=native with GCC9 on tigerlake machine.
> Bootstrapped and regtested
On Mon, Apr 12, 2021 at 11:53 PM H.J. Lu wrote:
>
> On Mon, Apr 12, 2021 at 2:21 AM Richard Biener
> wrote:
> >
> > On Sat, Apr 10, 2021 at 5:11 PM H.J. Lu via Gcc-patches
> > wrote:
> > >
> > > Add inline_ignore_target function attribute to inform the compiler that
> > > target specific option
Hi:
As described in PR, we introduced tigerlake string in driver-i386.c
by r9-8652 w/o support -march/tune=tigerlake which causes an error
when using -march/tune=native with GCC9 on tigerlake machine.
Bootstrapped and regtested on x86-64_iinux-gnu{-m32,}.
Ok for GCC9?
gcc/
*
Jakub Jelinek writes:
> Hi!
>
> Similarly to PR87763 for bfi, the GCC 9 combiner changes to not combine
> moves from hard registers regressed the following testcase where we no
> longer recognize bfxil and emit 3 instructions instead.
>
> The following patch adds define_insn patterns that match
Hello David and fellow GCC developers,
[the proposed patches for GCC trunk are at the end of the email]
I've been having way too much fun with your -fanalyzer code and
here are four patches which give the analyzer the ability to
understand the Modula-2 Storage API.
On 4/9/21 11:46 AM, Martin Storsjö wrote:
This is similar to what was done in
eea4e2ff0a3f5e7f37df204c070cc5d9ef339e6e (where it was added to
STAGE*_CXXFLAGS), but this adds the flag to the CXXFLAGS and
BOOT_CXXFLAGS variables too (as it's already added to CFLAGS and
BOOT_CFLAGS).
2021-04-09
On 4/9/21 11:46 AM, Martin Storsjö wrote:
This is similar to what was done in
eea4e2ff0a3f5e7f37df204c070cc5d9ef339e6e (where it was added to
STAGE*_CXXFLAGS), but this adds the flag to the CXXFLAGS and
BOOT_CXXFLAGS variables too (as it's already added to CFLAGS and
BOOT_CFLAGS).
2021-04-09
Hi,
I am following up to confirm if you (Gcc) are interested in acquiring the
Visitors/Registrants List.
Salon De L' Immobilier
28 - 30 May 2021
Rennes, France
Registrants Counts:4200
Each record of the list contains: Contact Name, Email Address, Company Name,
URL/Website, Phone No,
Hi!
Similarly to PR87763 for bfi, the GCC 9 combiner changes to not combine
moves from hard registers regressed the following testcase where we no
longer recognize bfxil and emit 3 instructions instead.
The following patch adds define_insn patterns that match what the combiner
is trying to match
On Mon, 12 Apr 2021, Jakub Jelinek wrote:
> Hi!
>
> Similarly to PR95450 done on GIMPLE, this patch punts if we try to
> simplify_{gen_,}subreg from some constant into the IBM double double
> IFmode (or sometimes TFmode) if the double double format wouldn't preserve
> the bits. Not all values
Hi,
stepping through the streaming process it turns out to be funny
difference between gimple_has_body and node->has_gimple_body_p.
While the first tests whether gimple body really exists in memory (by
looking for DECL_STRUCT_FUNCTION) the second tests if gimple body can be
made available via
50 matches
Mail list logo
