https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100751
--- Comment #16 from Gejoe ---
Created attachment 50881
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50881=edit
sample-prog.c edited to show __gcov_reset call.
The steps used for compiling and running the attached .c file are as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98636
David Binderman changed:
What|Removed |Added
CC||dcb314 at hotmail dot com
--- Comment
On 5/26/2021 11:29 AM, Andrew MacLeod via Gcc-patches wrote:
On 5/26/21 7:07 AM, Andrew Pinski wrote:
On Wed, May 26, 2021 at 2:01 AM Andrew Pinski wrote:
On Wed, May 26, 2021 at 1:43 AM Bernd Edlinger
wrote:
On 5/25/21 4:22 PM, Richard Biener via Gcc-patches wrote:
On Sun, May 23, 2021
On 5/28/21 6:42 AM, Bernd Edlinger wrote:
> Hi,
>
> I was wondering, why gimple-match.c and generic-match.c
> are not built early but always last, which slows down parallel
> makes significantly.
>
> The reason seems to be that generated_files does not
> mention gimple-match.c and
On 5/26/2021 5:18 PM, Martin Sebor via Gcc-patches wrote:
While checking objects whose addresses are passed to functions
declared to take const pointers and making sure they're initialized
the GCC 11 -Wmaybe-uninitialized enhancement assumes that the actual
argument is a pointer.
That's
On 5/27/21 11:59 PM, Jason Merrill wrote:
PR100797 seems like a P1 regression from 9.3, I'd like to fix it before
the release.
Here's a candidate patch. Going to bed now.
Jason
>From c5e228d0b49154e78feb8f64659ce491bdf118c1 Mon Sep 17 00:00:00 2001
From: Jason Merrill
Date: Thu, 27 May 2021
Hi,
I was wondering, why gimple-match.c and generic-match.c
are not built early but always last, which slows down parallel
makes significantly.
The reason seems to be that generated_files does not
mention gimple-match.c and generic-match.c.
This comment in Makefile.in says it all:
On 5/27/21 5:55 PM, David Malcolm wrote:
On Thu, 2021-05-27 at 10:41 -0600, Martin Sebor wrote:
On 5/27/21 5:19 AM, Richard Sandiford wrote:
Thanks for doing this.
Martin Sebor via Gcc-patches writes:
[…]
On 5/24/21 5:08 PM, David Malcolm wrote:
On Mon, 2021-05-24 at 16:02 -0600, Martin
On 5/27/2021 4:28 PM, Segher Boessenkool wrote:
On Thu, May 27, 2021 at 12:58:10PM -0700, H.J. Lu wrote:
You missed:
config/cr16/cr16.md: (clobber (cc0))]
config/cr16/cr16.md: [(parallel [(set (cc0)
config/cr16/cr16.md: [(set (cc0)
config/cr16/cr16.md: [(cc0) (const_int 0)]))]
PR100797 seems like a P1 regression from 9.3, I'd like to fix it before the
release.
On Tue, May 25, 2021 at 5:36 PM William Seurer via Gcc
wrote:
> Bootstrapped and tested it on powerpc64 power 7 and 8 BE and 8, 9, and
> 10 LE and saw nothing untoward.
>
> On 5/19/21 5:28 AM, Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100797
Jason Merrill changed:
What|Removed |Added
Priority|P3 |P1
On Mon, May 24, 2021 at 9:25 AM Philip Herron
wrote:
> Hi everyone,
>
> As some of you might know, I have been working on GCC Rust over on
> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving
> forward and enforcing GCC copyright assignments for contributors, I
> would like to
Hi Philip,
Philip Herron writes:
> As some of you might know, I have been working on GCC Rust over on
> GitHub https://github.com/Rust-GCC/gccrs. As the project is moving
> forward and enforcing GCC copyright assignments for contributors, I
> would like to create a branch on the GCC git repo to
On 5/27/21 6:07 PM, Matthias Kretz wrote:
On Thursday, 27 May 2021 23:15:46 CEST Jason Merrill wrote:
On 5/27/21 2:54 PM, Matthias Kretz wrote:
Also hiding all inline namespace by default might make some error messages
harder to understand:
namespace Vir {
inline namespace foo {
I chose option A, so everything is a size_t, now.
I also renamed the dyncast functions.
Here's the new patch.
Le jeudi 27 mai 2021 à 18:19 -0400, David Malcolm a écrit :
> On Tue, 2021-05-25 at 20:19 -0400, Antoni Boucher wrote:
> > @David: PING
> >
> > As far as I know, the only remaining
Here's the patch with the condition removed.
I believe everything is now fixed.
Thanks!
Le jeudi 27 mai 2021 à 18:21 -0400, David Malcolm a écrit :
> On Tue, 2021-05-25 at 20:16 -0400, Antoni Boucher wrote:
> > I updated the patch according to the comments by Tom Tromey.
> >
> > There's one
Dear Sir/Madam:
We understand from your information posted on Google.
that you are in the market for Plastic industry. We would like to take
this opportunity to introduce our company and products, with the hope
that we may work with Bright Ideas Imports in the future.
Our
Hi!
On Fri, May 21, 2021 at 02:45:18PM -0500, Peter Bergner wrote:
> Getting back to this now that trunk is open again...
>
> On 3/31/21 2:17 PM, Segher Boessenkool wrote:
> > On Tue, Mar 30, 2021 at 06:49:29PM -0500, Peter Bergner wrote:
> >> The mma_assemble_input_operand predicate does not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100804
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
---
On 27.05.21 21:58, Joseph Myers wrote:
On Thu, 27 May 2021, Tobias Burnus wrote:
@Joseph: I CC'ed you in case you have comments regarding
c-parser.c's c_parser_check_balanced_raw_token_sequence
Pilot error on my side – doing three things in parallel
(fixing a patch, updating docs + attending
Snapshot gcc-9-20210527 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/9-20210527/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 9 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
This patch removes HTML quoting from the Texinfo file gccgo.html.
Committed to mainline.
Ian
diff --git a/gcc/go/gccgo.texi b/gcc/go/gccgo.texi
index ce6b518bb7b..fa0e4882403 100644
--- a/gcc/go/gccgo.texi
+++ b/gcc/go/gccgo.texi
@@ -495,7 +495,7 @@ like (after importing the @code{os} package):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100805
Harald van Dijk changed:
What|Removed |Added
CC||harald at gigawatt dot nl
---
On Thu, May 27, 2021 at 12:58:10PM -0700, H.J. Lu wrote:
> You missed:
>
> config/cr16/cr16.md: (clobber (cc0))]
> config/cr16/cr16.md: [(parallel [(set (cc0)
> config/cr16/cr16.md: [(set (cc0)
> config/cr16/cr16.md: [(cc0) (const_int 0)]))]
> config/cr16/cr16.md: [(set (cc0)
>
On Tue, 2021-05-25 at 20:16 -0400, Antoni Boucher wrote:
> I updated the patch according to the comments by Tom Tromey.
>
> There's one question left about your question regarding
> C_MAYBE_CONST_EXPR, David:
>
> I am not sure if we can get a C_MAYBE_CONST_EXPR from libgccjit, and
> it
> indeed
Hi!
Whoops, I forgot to reply to this...
On Wed, May 05, 2021 at 06:25:49PM +, Koning, Paul wrote:
> > void g(void);
> > void h(void);
> > void i(void);
> > void f(long a, long b)
> > {
> >if (a < b)
> >g();
> >if (a == b)
> >h();
> >if
On Tue, 2021-05-25 at 20:19 -0400, Antoni Boucher wrote:
> @David: PING
>
> As far as I know, the only remaining question is about using
> `ssize_t`
> for the return type of some functions.
> Here's why I use this type:
>
> That seemed off to return NULL for the functions returning a
> size_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89370
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment #2
On Thursday, 27 May 2021 23:15:46 CEST Jason Merrill wrote:
> On 5/27/21 2:54 PM, Matthias Kretz wrote:
> > Also hiding all inline namespace by default might make some error messages
> > harder to understand:
> >
> > namespace Vir {
> >inline namespace foo {
> > struct A {};
> >}
> >
On Thu, 2021-05-27 at 10:41 -0600, Martin Sebor wrote:
> On 5/27/21 5:19 AM, Richard Sandiford wrote:
> > Thanks for doing this.
> >
> > Martin Sebor via Gcc-patches writes:
> > > […]
> > > On 5/24/21 5:08 PM, David Malcolm wrote:
> > > > On Mon, 2021-05-24 at 16:02 -0600, Martin Sebor wrote:
>
(Resend, the previous version messed up your questions and my answers,
hopefully this time it’s better)
Hi, Richard,
Thanks a lot for your comments.
On May 26, 2021, at 6:18 AM, Richard Biener
mailto:rguent...@suse.de>> wrote:
On Wed, 12 May 2021, Qing Zhao wrote:
Hi,
This is the 3rd
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100804
--- Comment #2 from George Thopas ---
After looking at the updated documentation and trying the an update kernel with
warning it still leaves some things open.
The updated documentation says:
"Moreover, the use of type punning or aliasing to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100805
--- Comment #1 from Andreas Schwab ---
The C++ standard says: [lex.icon] "If an integer literal cannot be represented
by any type in its list and an extended integer type (6.8.1) can represent its
value, it may have that extended integer type."
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100806
Bug ID: 100806
Summary: deadlock in std::counting_semaphore
Product: gcc
Version: 11.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
On 5/27/21 11:25 AM, Matthias Kretz wrote:
On Thursday, 27 May 2021 17:07:40 CEST Jason Merrill wrote:
On 5/26/21 5:29 PM, Matthias Kretz wrote:
New revision which can also be compiled with GCC 4.8.
From: Matthias Kretz
Ensure dump_template_decl for function templates never prints template
On 5/27/21 11:30 AM, Dr. Matthias Kretz wrote:
On Thursday, 27 May 2021 17:18:58 CEST Jason Merrill wrote:
On 5/26/21 5:27 PM, Matthias Kretz wrote:
From: Matthias Kretz
dump_type on 'const std::string' should not print 'const string' unless
TFF_UNQUALIFIED_NAME is requested.
On 5/27/21 2:54 PM, Matthias Kretz wrote:
On Thursday, 27 May 2021 19:39:48 CEST Jason Merrill wrote:
On 5/4/21 7:13 AM, Matthias Kretz wrote:
From: Matthias Kretz
This attribute overrides the diagnostics output string for the entity it
appertains to. The motivation is to improve QoI for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94490
Marek Polacek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100716
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:c33ec196aa713c62d73907dc8f9e57d7ab2e4e4b
commit r12-1100-gc33ec196aa713c62d73907dc8f9e57d7ab2e4e4b
Author: Matthias Kretz
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100763
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:27e906d5bb2e46e59fe4aa137317f3c8d49ecb44
commit r12-1099-g27e906d5bb2e46e59fe4aa137317f3c8d49ecb44
Author: Matthias Kretz
Date:
On 4/27/21 11:52 AM, Martin Sebor via Gcc-patches wrote:
On 4/27/21 8:04 AM, Richard Biener wrote:
On Tue, Apr 27, 2021 at 3:59 PM Martin Sebor wrote:
On 4/27/21 1:58 AM, Richard Biener wrote:
On Tue, Apr 27, 2021 at 2:46 AM Martin Sebor via Gcc-patches
wrote:
PR 90904 notes that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100805
Bug ID: 100805
Summary: __int128 should be disabled for non-extended -std=
options
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
On 5/25/21 2:59 AM, Eric Botcazou wrote:
[PATCH 2/11] use xxx_no_warning APIs in Ada.
Looks good to me, but remove the useless pair of parentheses in the 3rd hunk.
The hunk was actually incorrect, thanks for drawing my attention
to it! The second argument to the function is the option. To
There is no need to call ix86_fixup_binary_operands when there are
only one or no memory operands allowed.
2021-05-27 Uroš Bizjak
gcc/
* config/i386/mmx.md (addv2sf3): Do not call
ix86_fixup_binary_operands_no_copy.
(subv2sf3): Ditto.
(mulv2sf3): Ditto.
(v2sf3): Ditto.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96762
Michael Meissner changed:
What|Removed |Added
Last reconfirmed||2021-05-27
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99839
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
On Mon, May 24, 2021 at 1:23 PM Joseph Myers wrote:
>
> On Sat, 22 May 2021, H.J. Lu via Gcc-patches wrote:
>
> > 1. Update PUSH_ARGS to accept an argument. When the PUSH instruction
> > usage is optional, pass the number of bytes to push to PUSH_ARGS so that
> > the backend can decide if PUSH
Dear Fortranners,
frontend optimization tries to inline matmul, but then it also needs
to take care of the assignment to the result array. If that one is
not of canonical type, we currently get an ICE. The straightforward
solution is to simply punt in those cases and avoid inlining.
Regtested
1. Replace PUSH_ARGS with a target calls hook, TARGET_PUSH_ARGUMENT, which
takes an integer argument. When it returns true, push instructions will
be used to pass outgoing arguments. If the argument is nonzero, it is
the number of bytes to push and indicates the PUSH instruction usage is
On Thu, May 27, 2021 at 07:58:03PM +, Joseph Myers wrote:
> On Thu, 27 May 2021, Tobias Burnus wrote:
>
> > @Joseph: I CC'ed you in case you have comments regarding
> > c-parser.c's c_parser_check_balanced_raw_token_sequence (comment update)
> > and
On Mon, May 03, 2021 at 10:55:36PM +, Segher Boessenkool wrote:
> This removes CC0 and all directly related infrastructure.
>
> CC_STATUS, CC_STATUS_MDEP, CC_STATUS_MDEP_INIT, and NOTICE_UPDATE_CC
> are deleted and poisoned. CC0 is only deleted (some targets use that
> name for something
On Thu, 27 May 2021, Tobias Burnus wrote:
> @Joseph: I CC'ed you in case you have comments regarding
> c-parser.c's c_parser_check_balanced_raw_token_sequence (comment update)
> and c_parser_check_tight_balanced_raw_token_sequence (new); the latter
> is essentially cp_parser_skip_balanced_tokens
Hi, Richard,
Thanks a lot for your comments.
On May 26, 2021, at 6:18 AM, Richard Biener
mailto:rguent...@suse.de>> wrote:
On Wed, 12 May 2021, Qing Zhao wrote:
Hi,
This is the 3rd version of the patch for the new security feature for GCC.
Please take look and let me know your comments and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100463
Martin Sebor changed:
What|Removed |Added
Target Milestone|--- |12.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100463
--- Comment #7 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:5d05e83e243931c291409d4771f31747b6c04eb0
commit r12-1096-g5d05e83e243931c291409d4771f31747b6c04eb0
Author: Martin Sebor
Date:
Jason, I wonder if you could review this patch that Richard has
apparently decided to defer to others.
https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568901.html
Thanks
On 5/11/21 2:02 PM, Martin Sebor wrote:
Ping 2:
https://gcc.gnu.org/pipermail/gcc-patches/2021-April/568901.html
On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99895
Patrick Palka changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100653
Andrew Pinski changed:
What|Removed |Added
CC||george.thopas at gmail dot com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100804
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94490
Patrick Palka changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
On Thursday, 27 May 2021 19:39:48 CEST Jason Merrill wrote:
> On 5/4/21 7:13 AM, Matthias Kretz wrote:
> > From: Matthias Kretz
> >
> > This attribute overrides the diagnostics output string for the entity it
> > appertains to. The motivation is to improve QoI for library TS
> > implementations,
On Thu, May 27, 2021 at 08:30:33PM +0200, Tobias Burnus wrote:
> + if (c_parser_next_token_is (parser, CPP_NAME))
> +{
> + const char *p = IDENTIFIER_POINTER (c_parser_peek_token
> (parser)->value);
> + bool parse_iter = (strcmp ("iterator", p) == 0);
> + if (parse_iter)
I'd
@Joseph: I CC'ed you in case you have comments regarding
c-parser.c's c_parser_check_balanced_raw_token_sequence (comment update)
and c_parser_check_tight_balanced_raw_token_sequence (new); the latter
is essentially cp_parser_skip_balanced_tokens with slight adaptions.
On 27.05.21 10:22, Jakub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99893
Patrick Palka changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99893
--- Comment #2 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:fc3fdf0f2196e805a3a43ccb73595c33673670f3
commit r12-1095-gfc3fdf0f2196e805a3a43ccb73595c33673670f3
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100804
Bug ID: 100804
Summary: storage order swapped with specific opt
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100781
--- Comment #6 from Andrew Macleod ---
So the new code base provides a more complete/consistent export list, and makes
use of imports now. An import is the incoming value which can change an
outgoing value.
In this particular case we see:
:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100767
--- Comment #6 from Gabriel Marcano ---
I was the one that originally reported the issue on gcc-help, and I can confirm
that with the patch the segfault is no longer happening. I do appear to have
found a different bug (undefined references to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79328
Lucas Clemente Vella changed:
What|Removed |Added
CC||lvella at gmail dot com
---
On Linux/x86_64,
04ba00d4ed735242c5284d2c623a3a9d42d94742 is the first bad commit
commit 04ba00d4ed735242c5284d2c623a3a9d42d94742
Author: Uros Bizjak
Date: Thu May 27 09:22:01 2021 +0200
i386: Add uavg_ceil patterns for 4-byte vectors [PR100637]
caused
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86355
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:db79713150f4f8b6ff3de81d00d92578679e0e65
commit r12-1094-gdb79713150f4f8b6ff3de81d00d92578679e0e65
Author: Jason Merrill
Date:
This testcase revealed that we were using PACK_EXPANSION_EXTRA_ARGS a lot
more than necessary; use_pack_expansion_extra_args_p meant to use it in the
case of corresponding arguments in different argument packs differing in
whether they are pack expansions, but it was mistakenly also returning true
On 5/27/21 11:05 AM, Patrick Palka wrote:
Here, we're not finding the parameter pack inside the static_assert because
STATIC_ASSERT trees are tcc_exceptional, and we weren't explicitly walking
them in cp_walk_subtrees.
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
On 5/27/2021 10:00 AM, Martin Sebor via Gcc-patches wrote:
When attribute nonnull is applied to an argument of an erroneous
type the attribute positional argument validation function ICEs
while printing a warning that mentions the invalid type.
The attached patch changes the validation
On 5/4/21 7:13 AM, Matthias Kretz wrote:
From: Matthias Kretz
This attribute overrides the diagnostics output string for the entity it
appertains to. The motivation is to improve QoI for library TS
implementations, where diagnostics have a very bad signal-to-noise ratio
due to the long
We have been talking for a long time of a debug mode with less impact on
performances.
I propose to simply use the existing _GLIBCXX_ASSERTIONS macro.
libstdc++: [_GLIBCXX_ASSERTIONS] Activate basic debug checks
Use _GLIBCXX_ASSERTIONS as a _GLIBCXX_DEBUG light mode. When
defined it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100792
Joseph S. Myers changed:
What|Removed |Added
Version|tree-ssa|12.0
Status|RESOLVED
On 5/27/21 5:19 AM, Richard Sandiford wrote:
Thanks for doing this.
Martin Sebor via Gcc-patches writes:
[…]
On 5/24/21 5:08 PM, David Malcolm wrote:
On Mon, 2021-05-24 at 16:02 -0600, Martin Sebor wrote:
Subsequent patches then replace invocations of the TREE_NO_WARNING()
macro and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99453
--- Comment #15 from Jonathan Wakely ---
(In reply to Philippe Blain from comment #14)
> Out of curiosity, do you know what GDB does with this libstdc++.a-gdb.py ?
> It's there so it can be loaded manually I guess, but the auto-load behaviour
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67593
--- Comment #2 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:9b94785dedb08b006419bec1a402614d9241317a
commit r12-1093-g9b94785dedb08b006419bec1a402614d9241317a
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100779
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:9b94785dedb08b006419bec1a402614d9241317a
commit r12-1093-g9b94785dedb08b006419bec1a402614d9241317a
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96555
--- Comment #3 from CVS Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:9b94785dedb08b006419bec1a402614d9241317a
commit r12-1093-g9b94785dedb08b006419bec1a402614d9241317a
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100797
Patrick Palka changed:
What|Removed |Added
Target Milestone|9.5 |9.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100797
Patrick Palka changed:
What|Removed |Added
Summary|using declaration causing |[9/10/11/12 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100788
--- Comment #9 from seberg ---
NumPy is pretty light weight (at least on linux systems, and if you do not care
about setting up BLAS manually). You probably only need the Python dev
headers, that I expect you already have.
Hopefully, the
algorithms: zlib
gcc version 12.0.0 20210527 (experimental) [master revision
:d03f010a0:01c59ef2e5a59b44d2b662361196abb6be872a20] (GCC)
$ cat mutant.c
int bar();
__GIMPLE
int foo() {
if (bar())
goto bb1;
else
goto bb2;
}
$ gcc-trunk -fgimple mutant.c
mutant.c: In function ‘foo’:
mutant.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100774
--- Comment #2 from Andrew Macleod ---
I have a fix for this...
Do we add -fcompare-debug tests into the testsuite? I don't see any other
tests with it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100783
Martin Sebor changed:
What|Removed |Added
Summary|[10/11/12 Regression] ICE |[10/11/12 Regression] ICE
When attribute nonnull is applied to an argument of an erroneous
type the attribute positional argument validation function ICEs
while printing a warning that mentions the invalid type.
The attached patch changes the validation function to ignore
erroneous types on the assumption that they must
On Thursday, 27 May 2021 17:18:58 CEST Jason Merrill wrote:
> On 5/26/21 5:27 PM, Matthias Kretz wrote:
> > From: Matthias Kretz
> >
> > dump_type on 'const std::string' should not print 'const string' unless
> > TFF_UNQUALIFIED_NAME is requested.
> >
> > gcc/cp/ChangeLog:
> > PR c++/100763
On Thursday, 27 May 2021 17:07:40 CEST Jason Merrill wrote:
> On 5/26/21 5:29 PM, Matthias Kretz wrote:
> > New revision which can also be compiled with GCC 4.8.
> >
> > From: Matthias Kretz
> >
> > Ensure dump_template_decl for function templates never prints template
> > parameters after the
On 5/26/21 5:27 PM, Matthias Kretz wrote:
From: Matthias Kretz
dump_type on 'const std::string' should not print 'const string' unless
TFF_UNQUALIFIED_NAME is requested.
gcc/cp/ChangeLog:
PR c++/100763
* error.c: Call dump_scope when printing a typedef.
+ if (!
On 5/26/21 5:29 PM, Matthias Kretz wrote:
New revision which can also be compiled with GCC 4.8.
From: Matthias Kretz
Ensure dump_template_decl for function templates never prints template
parameters after the function name (it did with -fno-pretty-templates)
and skip output of irrelevant &
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100665
--- Comment #1 from Matthew Malcomson ---
Hi there.
I believe this is how it should work (if I'm understanding & remembering
correctly).
When creating a nested function, we make a single object on the stack that
includes all variables used in
Here, we're not finding the parameter pack inside the static_assert because
STATIC_ASSERT trees are tcc_exceptional, and we weren't explicitly walking
them in cp_walk_subtrees.
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK for
trunk?
gcc/cp/ChangeLog:
PR c++/99893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100795
--- Comment #5 from 康桓瑋 ---
(In reply to 康桓瑋 from comment #4)
> Same with ranges::make_heap, ranges::push_heap, ranges::pop_heap, and
> ranges::sort_heap when _GLIBCXX_CONCEPT_CHECKS is defined.
And std::ranges::shuffle.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100802
Bug ID: 100802
Summary: VRP fails to fold comparison with known value orders
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100795
--- Comment #4 from 康桓瑋 ---
Same with ranges::make_heap, ranges::push_heap, ranges::pop_heap, and
ranges::sort_heap when _GLIBCXX_CONCEPT_CHECKS is defined.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100783
Martin Sebor changed:
What|Removed |Added
Summary|[11/12 Regression] ICE |[10/11/12 Regression] ICE
On 5/26/21 10:51 PM, Joseph Myers wrote:
This commit breaks the build of glibc for powerpc64le-linux-gnu. Compile
the following code with -O2 -mlong-double-128 -mabi=ibmlongdouble and I
get the error
opts-bug.c:8:1: error: '-mabi=ibmlongdouble' requires '-mlong-double-128'
8 | {
|
1 - 100 of 199 matches
Mail list logo
