https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94092
Alexandre Oliva changed:
What|Removed |Added
Status|WAITING |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
--- Comment #17 from Richard Biener ---
(In reply to Martin Jambor from comment #16)
> For the IPA-CP ICE, I am still running some tests, but I am currently
> leaning towards the following. It might in theory disable IPA-CP in some
> strange K&R
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
--- Comment #18 from Richard Biener ---
Created attachment 50220
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50220&action=edit
patch
I am testing the following for the inline issue for the last testcase, leaving
the IPA CP one to you.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99158
Bug ID: 99158
Summary: [Enhancement] Better error message when missing
#include and using placement new
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98657
--- Comment #3 from CVS Commits ---
The master branch has been updated by Andre Simoes Dias Vieira
:
https://gcc.gnu.org/g:6070e39cd0af6ac4a88004c8b1b6a900a8bbce36
commit r11-7291-g6070e39cd0af6ac4a88004c8b1b6a900a8bbce36
Author: Andre Vieira
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98657
avieira at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #2 from Vittorio Zecca ---
I am sorry I should have taken more time analyzing this issue.
Actually it is not and infinite loop, I clocked the compilation first
with the -S option,
then with the -c option.
The compiler takes 4'52" of r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96966
--- Comment #5 from Richard Biener ---
(In reply to Jakub Jelinek from comment #4)
> Even
> extern char a[32];
>
> void f (const void *s)
> {
> char *p = (char*)__builtin_memcpy (a, s, 16);
> __builtin_memcpy (p, s, 16);
> }
>
>
> void g (
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99159
Bug ID: 99159
Summary: Confusing -Warray-bounds warning
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99153
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99027
--- Comment #3 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:f600f271b10d0214b111f2aa52a3d5740477e139
commit r11-7292-gf600f271b10d0214b111f2aa52a3d5740477e139
Author: Tobias Burnus
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99159
Andrew Pinski changed:
What|Removed |Added
Component|c |tree-optimization
--- Comment #1 from An
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99111
--- Comment #4 from CVS Commits ---
The releases/gcc-10 branch has been updated by Tobias Burnus
:
https://gcc.gnu.org/g:0f225e57427fd8ca1cdc63b6c2f3001493987474
commit r10-9375-g0f225e57427fd8ca1cdc63b6c2f3001493987474
Author: Tobias Burnus
D
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157
kratenko changed:
What|Removed |Added
CC||gcc-bugzilla at garstig dot org
--- Comment #
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99160
Bug ID: 99160
Summary: A wrong accessible check when using a
using-declaration that introduces the names of type
and function
Product: gcc
Version: 10.2.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99111
Tobias Burnus changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99161
Bug ID: 99161
Summary: Suboptimal SVE code for ld4/st4 MLA code
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
--- Comment #19 from Martin Jambor ---
(In reply to Richard Biener from comment #17)
> there's variably_modified_type_p (you can pass NULL_TREE for the fndecl)
> which is more to the point. Otherwise it looks reasonable. Does IPA CP
> do things
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
--- Comment #20 from Jakub Jelinek ---
I think you don't want variably_modified_type_p, that returns true even for
pointers to VLAs (and references etc., perhaps many times indirectly).
I think those should be fine, they are used fairly often unl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
--- Comment #21 from rguenther at suse dot de ---
On Fri, 19 Feb 2021, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
>
> --- Comment #20 from Jakub Jelinek ---
> I think you don't want variably_modified_t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97549
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99034
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:37bde2f87267908a93c07856317a28827f8284f7
commit r11-7294-g37bde2f87267908a93c07856317a28827f8284f7
Author: Jakub Jelinek
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99034
Jakub Jelinek changed:
What|Removed |Added
Summary|[9/10/11 Regression] error: |[9/10 Regression] error: EH
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99158
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Summary|[Enhancement] B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98998
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:1a132c4d7cdb22cbab85b8596418daa2c3157812
commit r11-7295-g1a132c4d7cdb22cbab85b8596418daa2c3157812
Author: Jakub Jelinek
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98998
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99162
Bug ID: 99162
Summary: problem when compile with O2 or O3
Product: gcc
Version: 4.9.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99163
Bug ID: 99163
Summary: Odd error message when using `main` with
-pedantic-errors
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98726
--- Comment #7 from avieira at gcc dot gnu.org ---
I'm looking at this and I have a feeling there is a disconnect on how some
passes define VECTOR_CST and how the expand pass handles it.
So the problem here seems to lie with the V4SImode VECTOR_C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98726
--- Comment #8 from avieira at gcc dot gnu.org ---
Also at some point we should figure out why the vectorizer is generating this
much code for this example, where I think it should be able to optimized it to:
a = 22;
b &= c;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210
--- Comment #9 from Jozef Lawrynowicz ---
I believe this PR only relates to the fact that GCC support for SHF_GNU_RETAIN
was available before GOLD supported that section flag.
My proposed patch was to turn off GCC support for SHF_GNU_RETAIN if a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99122
--- Comment #22 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:1a2a7096e5e20d736c6138179470b21aa5a74864
commit r11-7296-g1a2a7096e5e20d736c6138179470b21aa5a74864
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99153
--- Comment #1 from Nathan Sidwell ---
I think this is a duplicate of 99071, which hadn't been done when Mattias
tested.
However, I am getting a different ICE:
devvm1702:235>./xg++ -B./ -nostdinc++
-I../x86_64-pc-linux-gnu/libstdc++-v3/include
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99162
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99164
Bug ID: 99164
Summary: gccgo internal compiler error: alias receiver
Product: gcc
Version: 10.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99162
--- Comment #2 from Jonathan Wakely ---
(In reply to Zhang Haibin from comment #0)
> $ g++ --version
> g++ (GCC) 4.9.2
This compiler is ancient and we're not interested in bug reports for it.
If you use a modern compiler you can use -fsanitize=
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99163
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99165
Bug ID: 99165
Summary: [11 Regression] ICE in verify_dominators, at
dominance.c:1184 since r11-7205-g95d94b52ea847833
Product: gcc
Version: 11.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99165
Martin Liška changed:
What|Removed |Added
Target Milestone|--- |11.0
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99166
Bug ID: 99166
Summary: [modules] Unable to determine where CMI is being found
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98357
Andrew Macleod changed:
What|Removed |Added
CC||aldyh at redhat dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99164
Ian Lance Taylor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98967
Nathan Sidwell changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot
gnu.org
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99137
--- Comment #5 from Tobias Burnus ---
Iff it is decided that it is invalid code, the following patch rejects it:
https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565576.html
(I forgot to reload the PR before posting.)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99156
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-02-19
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
--- Comment #3 from Jonathan Wakely ---
(In reply to seurer from comment #0)
> 3 incompatible symbols
> 0
> _ZSt8to_charsPcS_g
> std::to_chars(char*, char*, __float128)
It took me a while to realise that these symbols are not __float128, they'r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98389
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99165
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99165
Martin Liška changed:
What|Removed |Added
Summary|[11 Regression] ICE in |ICE in verify_dominators,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
--- Comment #3 from Vittorio Zecca ---
I changed symbol.c as per your suggestion and now the address
sanitized gfortran compiles fine.
Now I am going to check it against the testsuite.
Results tomorow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157
--- Comment #2 from Hau Hsu ---
Created attachment 50221
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50221&action=edit
libgcc objdump result for gcc-7 and gcc-10
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98875
Mark Wielaard changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99157
--- Comment #3 from Hau Hsu ---
Here are some more info.
This check determines whether macro __ARM_FEATURE_CMSE is set to 3,
and affects CMSE support for function cmse_check_address_range():
void *
__attribute__ ((warn_unused_result))
cmse_chec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98890
--- Comment #4 from Tobias Burnus ---
Related issue but without an ICE:
contains
integer function f1()
!f2 = 1 ! gives an error as expected
j = f2! accepted; cast of function addr to integer(kind=4)
f1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
Bug ID: 99167
Summary: typo in params.opt: accesse
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: translation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99145
--- Comment #3 from Jerry DeLisle ---
Initially it is creating the very large string in the frontend passes and then
via resolution and translation phases, and finally into the middle-end and back
end phases where it I am guessing the optimizers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
Martin Liška changed:
What|Removed |Added
Last reconfirmed||2021-02-19
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
--- Comment #2 from CVS Commits ---
The master branch has been updated by Martin Liska :
https://gcc.gnu.org/g:c8d13835638ff82f3ba7bfb0a5c2f597851dfb5a
commit r11-7297-gc8d13835638ff82f3ba7bfb0a5c2f597851dfb5a
Author: Martin Liska
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99167
Martin Liška changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264
--- Comment #13 from seurer at gcc dot gnu.org ---
Thanks, that did fix it on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99168
Bug ID: 99168
Summary: inconsistent behavior on -O0 and -O2 with ASAN on
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98890
Jerry DeLisle changed:
What|Removed |Added
CC||jvdelisle at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99168
--- Comment #1 from zhan3299 at purdue dot edu ---
If we resolved the conflicts on "aligned", it would behave normally. I feel
like the ASAN is confused by the "aligned" somehow.
Should it have thrown some warnings?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91191
--- Comment #8 from Andrew Macleod ---
(In reply to Jeffrey A. Law from comment #7)
> If you're V_C_E-ing to a narrower type, you just ignore the bits outside the
> target type, it's a lot like a narrowing subreg in the RTL world.
>
> I don't kn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98875
--- Comment #5 from Mark Wielaard ---
https://gcc.gnu.org/pipermail/gcc-patches/2021-February/565587.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99146
--- Comment #1 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:72d91d6cd41f2987339a98c2c64f70b3850f4e0b
commit r11-7298-g72d91d6cd41f2987339a98c2c64f70b3850f4e0b
Author: Tobias Burnus
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99010
--- Comment #2 from CVS Commits ---
The master branch has been updated by Tobias Burnus :
https://gcc.gnu.org/g:f86e187e12db14ad1cced26b9f8aafb06498e208
commit r11-7299-gf86e187e12db14ad1cced26b9f8aafb06498e208
Author: Tobias Burnus
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99010
Tobias Burnus changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99146
Tobias Burnus changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98210
Jozef Lawrynowicz changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|REOPENED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98890
--- Comment #6 from Jerry DeLisle ---
I should have noted in the above case, if we remove the parens on line 5,
k = f1 is rejected.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
Bug ID: 99169
Summary: Segfault when passing allocatable scalar into
intent(out) dummy argument
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99166
Nathan Sidwell changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99159
Martin Sebor changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97172
--- Comment #29 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:3599ecb6a0145a428def5314d2d67d2e5a88f3c4
commit r11-7301-g3599ecb6a0145a428def5314d2d67d2e5a88f3c4
Author: Martin Sebor
Date: Fri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99147
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:af027826292351218785f893d1c42fe28ae3ed9f
commit r11-7303-gaf027826292351218785f893d1c42fe28ae3ed9f
Author: Harald Anlauf
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264
Peter Bergner changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to work||8.4.1
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
--- Comment #2 from anlauf at gcc dot gnu.org ---
Note/workaround: the {CLOBBER} disappears if the argument to set_i is declared
INOUT instead of OUT.
ultilib CC=gcc-9 CXX=g++-9 --enable-languages=c,c++,fortran,lto,objc
--no-create --no-recursion
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 11.0.0 20210219 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-std=c++20' '-fm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99170
--- Comment #1 from Rémi Galan Alfonso ---
Created attachment 50224
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50224&action=edit
preprocessed file
... And with the correct preprocessed file this time, apologies for my mistake.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
--- Comment #3 from anlauf at gcc dot gnu.org ---
A conservative solution simply disables the clobber:
diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c
index 103cb31c664..ce7bfaa89e8 100644
--- a/gcc/fortran/trans-expr.c
+++ b/gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
--- Comment #7 from Vladimir Makarov ---
Created attachment 50225
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50225&action=edit
A candidate patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96264
seurer at gcc dot gnu.org changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||tkoenig at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97366
--- Comment #8 from Vladimir Makarov ---
I've tried different approaches to fix it. The best patch I have now is in the
attachment.
Unfortunately, the best patch results in two new failures on ppc64 (other
patches are even worse):
gcc.target/p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99171
Bug ID: 99171
Summary: [10 Regression] Optional procedure call inside Open MP
parallel loop produces Segmentation Fault
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98686
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jerry DeLisle :
https://gcc.gnu.org/g:dfa2f821c18b7e926b5f5d6e394a0c915937db5e
commit r11-7306-gdfa2f821c18b7e926b5f5d6e394a0c915937db5e
Author: Jerry DeLisle
Date: Fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99172
Bug ID: 99172
Summary: Build failure with slibtool and vtv
Product: gcc
Version: 10.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99169
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
gnu.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98741
--- Comment #2 from CVS Commits ---
The master branch has been updated by Nathan Sidwell :
https://gcc.gnu.org/g:14886cbe300c144a4390245d0515cdf28fc5f68f
commit r11-7307-g14886cbe300c144a4390245d0515cdf28fc5f68f
Author: Nathan Sidwell
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98741
Nathan Sidwell changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99156
--- Comment #2 from zhan3299 at purdue dot edu ---
(In reply to Martin Liška from comment #1)
> Yes, I can confirm the issue. Thanks for the report.
Many thanks for your prompt reply. Additionally, I have to give credit to
Richard Smith for findi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99173
Bug ID: 99173
Summary: new test case c-c++-common/attr-retain-5.c added in
r11-7284 fails
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99174
Bug ID: 99174
Summary: [modules] ICE with recursive inclusion of header-unit
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99153
--- Comment #2 from Nathan Sidwell ---
// B_a.ii
template
struct pair
{
inline void Frob ();
};
// B_b.ii
import "./B_a.ii"
template
inline void pair<_T1>::Frob()
{ }
./cc1plus -quiet -std=c++20 -fmodule-header -fpreprocessed B_a.ii && .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99173
--- Comment #1 from seurer at gcc dot gnu.org ---
There are actually a bunch more. Here's the full list:
FAIL: c-c++-common/attr-retain-5.c -Wc++-compat (test for excess errors)
FAIL: c-c++-common/attr-retain-5.c -std=gnu++14 (test for excess
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99175
Bug ID: 99175
Summary: FAIL: g++.dg/modules/bad-mapper-1.C -std=c++17 (test
for errors, line )
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
1 - 100 of 112 matches
Mail list logo
