https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> Right the problem is here (and not with the compiler itself if there is a
> problem):
> /home/ubuntu/upstream-gcc/include/c++/11.0.1/ostream:747:46: error: no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692
Andrew Pinski changed:
What|Removed |Added
Component|c++ |libstdc++
--- Comment #1 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98736
--- Comment #4 from bin cheng ---
(In reply to bin cheng from comment #3)
> hmm, seems topological order isn't enough for distributing a loop nest, we
> need topological order plus inner loop depth-first.
Well, not really. In this case,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99692
Bug ID: 99692
Summary: Lookup for operator<< skips global scope
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99691
Bug ID: 99691
Summary: OpenBSD support for GDC
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee:
Snapshot gcc-10-20210320 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/10-20210320/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 10 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31235
Eric Gallager changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71009
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org,
Following your feedback here is the simplified version. I grouped it
with the patch I submitted before.
On 19/03/21 8:41 pm, Jonathan Wakely wrote:
On 16/03/21 21:55 +0100, François Dumont via Libstdc++ wrote:
Following:
https://gcc.gnu.org/pipermail/libstdc++/2021-March/052158.html
Here
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99689
Andrew Pinski changed:
What|Removed |Added
Component|c++ |middle-end
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99688
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
Hi.
The patch fixes the alloc-dealloc-mismatch reported by ASAN.
Patch can bootstrap on x86_64-linux-gnu and survives regression tests.
Ready to be installed?
Thanks,
Martin
gcc/cp/ChangeLog:
PR c++/99687
* module.cc (fini_modules): Call vec_free instead of delete.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99690
Bug ID: 99690
Summary: gcc/config/m68k/t-mlibs doesn't allow extending
MULTILIB_EXCEPTIONS
Product: gcc
Version: 7.5.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97491
--- Comment #9 from CVS Commits ---
The releases/gcc-9 branch has been updated by Harald Anlauf
:
https://gcc.gnu.org/g:e016c286dae10ea1b037d149fee924bdd07e546a
commit r9-9298-ge016c286dae10ea1b037d149fee924bdd07e546a
Author: Harald Anlauf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99689
--- Comment #1 from Soren Soe ---
Created attachment 50440
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50440=edit
source file
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99689
Bug ID: 99689
Summary: Initialized local variable becomes uninitialized after
use
Product: gcc
Version: 9.3.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99688
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99688
Bug ID: 99688
Summary: AddressSanitizer: stack-buffer-overflow on address at
gfc_match_name(char*) gcc/fortran/match.c:685
Product: gcc
Version: 11.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99687
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99687
Martin Liška changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99687
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-03-20
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99687
Bug ID: 99687
Summary: AddressSanitizer: alloc-dealloc-mismatch (malloc vs
operator delete) on 0x60400d50
Product: gcc
Version: 11.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99675
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-03-20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99686
--- Comment #1 from Steven Sun ---
The compiler args are only "g++ -fconcepts -std=c++17"
It should choose the full specialization func(int &&), while the compiler
aborts during the instatiation of the partial specialization (using concepts).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99686
Bug ID: 99686
Summary: ICE when concepts on C++17 when providing both T&& and
const T& specialization
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Hi,
I am Namitha S, an undergrad from Amrita University. This mail is regarding
GSOC-2021, I wanted to know more about the project "Extend the static
analysis pass". I've gone through the wiki and finished the tasks listed
out in the before you apply section. I've already read the mail replies
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99685
Bug ID: 99685
Summary: gcc.target/powerpc/divkc3-1.c and mulkc3-1.c fails for
32 bits
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
) 11.0.1 20210320 (experimental) [master branch],
configured with '--enable-languages=c,c++ --disable-multilib', built as docker
image on macOS 10.14.6
Dockerfile:
https://raw.githubusercontent.com/beanandbean/docker-gcc-cxx-modules/5fa616ae6c55bdb2c2961feff8d8ae5c51004961/Dockerfile
[with argument
On Sat, 20 Mar 2021, Jeff Law wrote:
> > > I think what you're trying to do here is set up a scenario where you're
> > > defaulting to mips32r6 and compact-branches, but not error if something
> > > specifies -mcpu=mips32r2 or something similar, right?
> > >
> > Yes. If we introduce the build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99683
Bug ID: 99683
Summary: Deduction failure when using CTAD of CNTTP inside a
deduction guide
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99679
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99679
--- Comment #1 from CVS Commits ---
The master branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:19ff0b0d816e6e7d7657a8559e9957d79dc1d77f
commit r11-7751-g19ff0b0d816e6e7d7657a8559e9957d79dc1d77f
Author: H.J. Lu
Date: Sat Mar 20
On Sat, Mar 20, 2021 at 4:55 PM H.J. Lu wrote:
>
> On Sat, Mar 20, 2021 at 6:46 AM Martin Liška wrote:
> >
> > On 3/20/21 1:21 PM, H.J. Lu wrote:
> > > |Since construct_container may be called with cfun == NULL, check cfun !=
> > > NULL before accessing silent_p. |
> >
> > Thank you for the
On 3/18/2021 4:18 PM, Martin Sebor via Gcc-patches wrote:
Ping:
https://gcc.gnu.org/pipermail/gcc-patches/2021-January/564483.html
The review of this patch digressed into a design discussion of a new,
more capable implementation of -Wstrict-aliasing, but the proposed
patch turning just this
Hi Kyrylo,
On Tue, 26 Jan 2021, Kyrylo Tkachov via Gcc-patches wrote:
> This patch adds the arm and aarch64 sections changes.html for GCC 11.
this is nice!
One question: why GCC 11.0 in the following? The first release is going
to be GCC 11.1, and we general refer to major releases - could we
---
gcc/pdbout.c | 28 +++-
1 file changed, 27 insertions(+), 1 deletion(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index d9ad659cd9a..0f5315f7f07 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -2175,7 +2175,33 @@ get_tree_name (tree t)
static const char anon_ns[] =
---
gcc/pdbout.c | 226 ++-
gcc/pdbout.h | 2 +
2 files changed, 170 insertions(+), 58 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 0f5315f7f07..b4528fb79e8 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -71,6 +71,7 @@ static void
---
gcc/pdbout.c | 151 ++-
gcc/pdbout.h | 1 +
2 files changed, 151 insertions(+), 1 deletion(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 3d15c620db5..d9ad659cd9a 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -84,7 +84,7 @@ static struct
---
gcc/pdbout.c | 256 ++-
gcc/pdbout.h | 1 +
2 files changed, 254 insertions(+), 3 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 8dbd8f58a87..3d15c620db5 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -1438,7 +1438,8 @@
---
gcc/pdbout.c | 208 ++-
gcc/pdbout.h | 10 +++
2 files changed, 217 insertions(+), 1 deletion(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index dae5c1ef679..8dbd8f58a87 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -79,6 +79,7 @@ static
---
gcc/pdbout.c | 79 +++-
1 file changed, 78 insertions(+), 1 deletion(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 0cae4d33469..dae5c1ef679 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -3344,6 +3344,8 @@ alias_hasher::equal (const
---
gcc/pdbout.c | 346 ++-
1 file changed, 344 insertions(+), 2 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index fb40f066bd9..0cae4d33469 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -73,6 +73,7 @@ static void pdbout_end_block
---
gcc/pdbout.c | 93 ++--
gcc/pdbout.h | 8 +
2 files changed, 99 insertions(+), 2 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 7d493513e06..d3f251f22d2 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -85,6 +85,7 @@ static
---
gcc/pdbout.c | 93 ++--
1 file changed, 91 insertions(+), 2 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index d3f251f22d2..fb40f066bd9 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -1484,24 +1484,113 @@ pdbout_finish (const char
---
gcc/pdbout.c | 469 ++-
gcc/pdbout.h | 51 ++
2 files changed, 517 insertions(+), 3 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 9701aaf8902..3bfec519877 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -83,6 +83,7 @@ static
---
gcc/pdbout.c | 62 +++-
gcc/pdbout.h | 1 +
2 files changed, 57 insertions(+), 6 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 3bfec519877..7d493513e06 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -829,6 +829,7 @@ free_type
---
gcc/pdbout.c | 449 +++
gcc/pdbout.h | 43 +
2 files changed, 492 insertions(+)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 5089203e339..9701aaf8902 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -46,6 +46,8 @@
#define
---
gcc/pdbout.c | 133 +++
gcc/pdbout.h | 15 ++
2 files changed, 148 insertions(+)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index fa3b1fb0312..8376b0e762c 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -79,6 +79,7 @@ static struct pdb_type
---
gcc/pdbout.c | 76 +++-
gcc/pdbout.h | 22 +++
2 files changed, 97 insertions(+), 1 deletion(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 8376b0e762c..5089203e339 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -55,6 +55,7 @@
---
gcc/pdbout.c | 85
gcc/pdbout.h | 11 +++
2 files changed, 96 insertions(+)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 08bb14364e5..fa3b1fb0312 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -78,6 +78,7 @@ static struct pdb_type
---
gcc/pdbout.c | 338 ++-
gcc/pdbout.h | 23
2 files changed, 359 insertions(+), 2 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 040ac6fe8e4..64f7c1d71bc 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -32,6 +32,7 @@
#include
---
gcc/pdbout.c | 131 ---
gcc/pdbout.h | 36 ++
2 files changed, 161 insertions(+), 6 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 64f7c1d71bc..08bb14364e5 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -76,6 +76,7 @@
---
gcc/pdbout.c | 150 ++-
gcc/pdbout.h | 10
2 files changed, 159 insertions(+), 1 deletion(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index a4424fa470d..040ac6fe8e4 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -54,6 +54,11 @@ static
---
gcc/pdbout.c | 195 ++-
gcc/pdbout.h | 16 +
2 files changed, 209 insertions(+), 2 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 29b0d1c131f..a4424fa470d 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -32,6 +32,7 @@
---
gcc/pdbout.c | 1272 +-
gcc/pdbout.h | 969 ++
2 files changed, 2238 insertions(+), 3 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 17011134d7a..2f5b52b6fc3 100644
--- a/gcc/pdbout.c
+++
---
gcc/pdbout.c | 242 ++-
gcc/pdbout.h | 21 +
2 files changed, 260 insertions(+), 3 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index 2f5b52b6fc3..29b0d1c131f 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -51,6 +51,7 @@ static
---
gcc/pdbout.c | 417 ++-
gcc/pdbout.h | 89 +++
2 files changed, 504 insertions(+), 2 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index e8f39bb64ea..feaab37cc37 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -25,13 +25,37 @@
---
gcc/pdbout.c | 149 +--
gcc/pdbout.h | 12 +
2 files changed, 158 insertions(+), 3 deletions(-)
diff --git a/gcc/pdbout.c b/gcc/pdbout.c
index feaab37cc37..17011134d7a 100644
--- a/gcc/pdbout.c
+++ b/gcc/pdbout.c
@@ -29,14 +29,25 @@
This is a series of patches to allow gcc to emit debugging information
in the PE-specific CodeView format, which allows Microsoft debuggers to
work with mingw EXEs. The format is semi-documented: Microsoft have
open-sourced some of their header files at
https://github.com/microsoft/microsoft-pdb,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
--- Comment #5 from Vladimir Makarov ---
(In reply to Jakub Jelinek from comment #4)
> I was worried that letters that introduce multi-letter constraints followed
> by '\0' could be a problem too. Or do we rely on those being dropped
> already
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99230
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:9f59cb7cac009f3c6eba81eb09714699b9ac9f8d
commit r11-7750-g9f59cb7cac009f3c6eba81eb09714699b9ac9f8d
Author: Jakub Jelinek
Date:
On Sat, Mar 20, 2021 at 6:46 AM Martin Liška wrote:
>
> On 3/20/21 1:21 PM, H.J. Lu wrote:
> > |Since construct_container may be called with cfun == NULL, check cfun !=
> > NULL before accessing silent_p. |
>
> Thank you for the quick fix.
>
> Please use the minimal reproducer for a test-case:
>
On 3/3/2021 8:33 PM, yunqiang...@cipunited.com wrote:
On 2/23/21 3:14 AM, YunQiang Su wrote:
For MIPSr6, we may wish to use compact-branches only.
Currently, we have to use `always' option, while it is mark as
conflict with pre-R6.
cc1: error: unsupported combination: ‘mips32r2’
On 3/12/2021 10:54 AM, Stefan Schulze Frielinghaus via Gcc-patches wrote:
In addition to the existing check also ask the target whether a
replacement register may be accessed in a different mode than it was set
before.
Bootstrapped and regtested on IBM Z. Ok for mainline?
gcc/ChangeLog:
On 3/18/2021 2:48 AM, Jakub Jelinek via Gcc-patches wrote:
Hi!
The following testcase results in -fcompare-debug failure.
The problem is the similar like in PR94272
https://gcc.gnu.org/pipermail/gcc-patches/2020-March/542562.html
When genericizing, with -g0 we have just a TREE_SIDE_EFFECTS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
--- Comment #4 from Jakub Jelinek ---
I was worried that letters that introduce multi-letter constraints followed by
'\0' could be a problem too. Or do we rely on those being dropped already
earlier?
Something like "=B" on x86_64 etc. In what
On 3/9/2021 11:30 PM, Alexandre Oliva wrote:
The test expects shrink-wrapping of the fsqrt call, but that will only
occur when there is a usable sqrt insn.
Arrange for dejagnu to add the options that enable the sqrt insn, if
one is available, and to skip the test otherwise.
H-P, this
On 3/7/2021 4:10 PM, Ahamed Husni via Gcc-patches wrote:
Hi all,
This is my first contribution for an open source project. Please guide
me if anything is missing.
diff --git a/gcc/gcc/asan.c b/gcc/gcc/asan.c
index 89ecd99b182..836f50bd44a 100755
--- a/gcc/gcc/asan.c
+++ b/gcc/gcc/asan.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99682
Bug ID: 99682
Summary: [modules] Module implementation unit is unable to
indirectly import its corresponding interface unit
Product: gcc
Version: 11.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97134
Omer Rosler changed:
What|Removed |Added
CC||omer.rosler at gmail dot com
--- Comment
The following patch fixes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
The patch was successfully bootstrapped on x86-64.
commit c1ab0c0336d85f5e97739060ecf77fd05ac86d2a
Author: Vladimir N. Makarov
Date: Sat Mar 20 10:50:03 2021 -0400
[PR99680] Check empty constraint before using
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
--- Comment #3 from CVS Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:8bf983c71e42d5a9f9df8a7dc436b30cd9da42f5
commit r11-7748-g8bf983c71e42d5a9f9df8a7dc436b30cd9da42f5
Author: Vladimir N. Makarov
On Sat, Mar 20, 2021 at 3:58 AM Jonathan Wakely wrote:
>
>
>
> On Sat, 20 Mar 2021, 01:13 Tim Song via Libstdc++,
> wrote:
>>
>> On Fri, Mar 19, 2021 at 3:13 PM Jonathan Wakely via Libstdc++
>> wrote:
>> >
>> > Implement this C++23 feature, as proposed by P1048R1.
>> >
>> > This implementation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
--- Comment #2 from Vladimir Makarov ---
Sorry for the troubles with my previous patch. I should have not be in hurry to
fix PR99663.
I'll fix it today. Jakub's patch could be a candidate but I prefer check
constraint[0] on '\0'.
On 3/20/21 1:21 PM, H.J. Lu wrote:
|Since construct_container may be called with cfun == NULL, check cfun != NULL
before accessing silent_p. |
Thank you for the quick fix.
Please use the minimal reproducer for a test-case:
$ cat va-arg-pack-1.C
#include
void abort() {
double ld;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
Hey,
I'm a student at Delhi Technological University, and interested in
contributing to the *Make cp-demangle non-recursive* and *Fortran improved
argument compile-time checking*. Before reaching out here In the past week
I have gone through most of the introduction wiki on building and testing,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99673
--- Comment #2 from Arnd Bergmann ---
Thank you for the detailed analysis. This was the last such warning I get with
linux kernel randconfig build that I could not explain based on the earlier
discussion, so now I can submit the local
Since construct_container may be called with cfun == NULL, check
cfun != NULL before accessing silent_p.
gcc/
PR target/99679
* config/i386/i386.c (construct_container): Check cfun != NULL
before accessing silent_p.
gcc/testsuite/
PR target/99679
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99681
Martin Liška changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99681
Bug ID: 99681
Summary: [11 Regression] ICE in print_shift_count_operand, at
config/s390/s390.c:7630
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
Martin Liška changed:
What|Removed |Added
Ever confirmed|0 |1
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99680
Bug ID: 99680
Summary: [11 Regression] AddressSanitizer:
global-buffer-overflow since g:04b4828c6dd2
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99508
--- Comment #6 from Frank Mehnert ---
Fix confirmed. Thanks guys!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99679
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-03-20
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99679
Bug ID: 99679
Summary: [11 Regression] ICE in construct_container at
gcc/config/i386/i386.c:2571 since
g:5e2eabe1eed1e53d39923517122d3c7de2013ad4
Product: gcc
Hi Jerry and Steve,
Yes Ok for trunk.
Thanks for the heads-up and the review, committed as r11-7742.
Best regards
Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99334
--- Comment #7 from Jakub Jelinek ---
#c6 reproduces even on current trunk with
-fno-tree-sink -O3 -fPIC -fomit-frame-pointer -fno-strict-aliasing
-mstackrealign
On Sat, 20 Mar 2021, 01:13 Tim Song via Libstdc++,
wrote:
> On Fri, Mar 19, 2021 at 3:13 PM Jonathan Wakely via Libstdc++
> wrote:
> >
> > Implement this C++23 feature, as proposed by P1048R1.
> >
> > This implementation assumes that a C++23 compiler supports concepts
> > already. I don't see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99546
--- Comment #4 from 康桓瑋 ---
same form, but this will trigger ICE:
struct S{
constexpr static auto s = requires { []; };
};
:1:8: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99563
--- Comment #8 from andysem at mail dot ru ---
Thanks again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99636
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99626
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99563
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99542
Jakub Jelinek changed:
What|Removed |Added
Summary|[9/10 Regression] ICE in|[9 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99517
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99362
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99324
Jakub Jelinek changed:
What|Removed |Added
Summary|[8/9/10 Regression] ICE in |[8/9 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85099
Bug 85099 depends on bug 99085, which changed state.
Bug 99085 Summary: [10 Regression] ICE: verify_flow_info failed (error:
multiple hot/cold transitions found)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99085
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99085
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
1 - 100 of 115 matches
Mail list logo
