https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87066
--- Comment #2 from Marc Glisse ---
I am not convinced that rejecting new B[1] is a good idea, you could also
change the standard to say that it is ok. The destructor is only useful here
if, for new B[2], the first B is constructed ok but the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87067
Bug ID: 87067
Summary: [8.1, 8.2] LTO-related ICE when running armv7 binutils
test suite
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87022
bin cheng changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77684
--- Comment #9 from Martin Sebor ---
Andi, we keep seeing intermittent failures in these tests. Can you help?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87061
--- Comment #3 from Jonathan Wakely ---
Author: redi
Date: Wed Aug 22 22:54:33 2018
New Revision: 263791
URL: https://gcc.gnu.org/viewcvs?rev=263791=gcc=rev
Log:
PR libstdc++/87061 remove pmr type aliases for COW strings
The pmr aliases for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87061
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87066
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78448
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78448
--- Comment #4 from Jonathan Wakely ---
Author: redi
Date: Wed Aug 22 22:22:40 2018
New Revision: 263789
URL: https://gcc.gnu.org/viewcvs?rev=263789=gcc=rev
Log:
PR libstdc++/78448 limit vector::max_size and deque::max_size
The container
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87066
Bug ID: 87066
Summary: new expression and potential destructor invokation
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87065
--- Comment #2 from David Binderman ---
It also seems to have been going wrong since sometime before
revision 262835.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87065
--- Comment #1 from David Binderman ---
Reduced C code is this:
a, b, c, d, e;
f() {
short *g = b;
int h = 1;
for (; h <= 1; h++)
g =
unsigned i;
for (; c; c++) {
for (; i <= 1; i++)
;
a ^= (a > 0 <= i) + ((e += d)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87065
Bug ID: 87065
Summary: ice in trunc_int_for_mode
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87064
Bug ID: 87064
Summary: [9 regression] libgomp.oacc-fortran/reduction-3.f90
fails starting with r263751
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
--- Comment #6 from Konstantin Kharlamov ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Konstantin Kharlamov from comment #2)
> > As far as such trivial optimizations concerned, I'd prefer to rely on the
> > compiler figuring
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87031
--- Comment #5 from Michael_S ---
It's fine that you moved the 2nd case to 'tree-optimization'. I suppose that's
where it belongs.
But I just saw the second case by chance in the process of reduction of the
first case to bare minimum. For me it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87021
--- Comment #1 from Will Schmidt ---
These should clear up once the gimple-folding for vec_splat() code goes in.
If that patch is held up much longer (relatively), i will probably disable the
scan-assembler counts for those tests.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87031
--- Comment #4 from Michael_S ---
It's fine that you moved the 2nd case to 'tree-optimization'. I suppose that's
where it belongs.
But I just saw the second case by chance in the process of reduction of the
first case to bare minimum. For me it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86957
--- Comment #3 from Indu Bhagat ---
Currently, GCC dumps some information in the dump files regarding functions not
being executed in the training run (And, I agree its not satisfactorily
direct).
First, in the "Symbol table:" dump section in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86935
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79342
--- Comment #9 from H.J. Lu ---
A patch is posted at
https://gcc.gnu.org/ml/gcc-patches/2018-08/msg01389.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86935
--- Comment #2 from janus at gcc dot gnu.org ---
Author: janus
Date: Wed Aug 22 19:31:40 2018
New Revision: 263787
URL: https://gcc.gnu.org/viewcvs?rev=263787=gcc=rev
Log:
fix PR 86935
2018-08-22 Janus Weil
PR fortran/86935
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
--- Comment #5 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Konstantin Kharlamov from comment #2)
> > (In reply to Jonathan Wakely from comment #1)
> > > That would require a lot of special-casing just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68222
François Dumont changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
--- Comment #4 from Jonathan Wakely ---
(In reply to Konstantin Kharlamov from comment #2)
> (In reply to Jonathan Wakely from comment #1)
> > That would require a lot of special-casing just for std::variant.
>
> Well, I think, in place of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68222
--- Comment #2 from François Dumont ---
Author: fdumont
Date: Wed Aug 22 18:51:25 2018
New Revision: 263786
URL: https://gcc.gnu.org/viewcvs?rev=263786=gcc=rev
Log:
2018-08-22 François Dumont
PR libstdc++/68222
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87061
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87063
Bug ID: 87063
Summary: Const subobject with const assignment operator, but
operator anyway deleted
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87050
Gerald Pfeifer changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87060
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87062
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87047
--- Comment #5 from Alexander Monakov ---
... and avoiding the wrong branch fixes this bug without regressing pr78120.c
testcase:
--- a/gcc/ifcvt.c
+++ b/gcc/ifcvt.c
@@ -3413,7 +3413,7 @@ noce_process_if_block (struct noce_if_info *if_info)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87062
--- Comment #1 from Tom Tromey ---
Analysis in the comments there puts the blame on -ftree-slp-vectorize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87062
Bug ID: 87062
Summary: mis-optimized code with -O3 and std::pair
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86837
Thomas Koenig changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39627
Bug 39627 depends on bug 86888, which changed state.
Bug 86888 Summary: [F08] allocatable components of indirectly recursive type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86888
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86888
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87061
Bug ID: 87061
Summary: [9 Regression] regex cannot be compiled with
-std=c++1z -D_GLIBCXX_USE_CXX11_ABI=0
Product: gcc
Version: 9.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86888
--- Comment #2 from janus at gcc dot gnu.org ---
Author: janus
Date: Wed Aug 22 17:10:00 2018
New Revision: 263782
URL: https://gcc.gnu.org/viewcvs?rev=263782=gcc=rev
Log:
fix PR 86888
2018-08-22 Janus Weil
PR fortran/86888
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86973
--- Comment #3 from Michael Matz ---
A testcase that doesn't need -mabi cmdline args:
extern __attribute__((ms_abi)) void foo(void);
__attribute__((sysv_abi))
void a(__attribute__((__vector_size__(8 * sizeof(double double b){
foo();
}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64949
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
CC||qinzhao at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87052
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87052
Martin Sebor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87030
Iain Sandoe changed:
What|Removed |Added
CC||iains at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86983
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86771
--- Comment #21 from Segher Boessenkool ---
Author: segher
Date: Wed Aug 22 16:04:09 2018
New Revision: 263780
URL: https://gcc.gnu.org/viewcvs?rev=263780=gcc=rev
Log:
[ fix changelog ]
2018-08-22 Segher Boessenkool
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
--- Comment #2 from Aldy Hernandez ---
I can't reproduce with a cross to powerpc64le-linux.
I'm trying this:
void d(void);
char *a, *b;
void c(void) {
if (b == a)
return;
if (__builtin_strncmp(a, "", b - a))
d();
}
I also tried
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87003
--- Comment #2 from Tom Tromey ---
I don't really know the best thing to do.
I see your point about graceful failure being a useful
feature, in cases where the result of some gcc-jit function
is passed as an argument to another one.
Maybe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86973
Martin Liška changed:
What|Removed |Added
Known to work|5.4.0 |
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86973
--- Comment #1 from Michael Matz ---
I can reproduce the same error without any va-args:
% cat bug.i
extern void foo(void *);
__attribute__((sysv_abi))
void a(__attribute__((__vector_size__(8 * sizeof(double double b){
foo(0);
}
% ./cc1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87060
--- Comment #1 from Yevheniy Soloshenko ---
Ok, my fault. Integer promotion in action.
The code below is fine.
```
void test_u8 (void)
{
if ((unsigned char)(u8 + 1)) { u8 = 1; }
}
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87060
Bug ID: 87060
Summary: Condition check is optimized out for volatile unsigned
char / short
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80080
--- Comment #12 from Ilya Leoshkevich ---
I've investigated foo3, foo4 and foo5, and came to the following
conclusions:
When foo3 is compiled with -march=z10 or later, cprop1 pass propagates
global's SYMBOL_REF value into UNSPECV_CAS. On
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87015
--- Comment #4 from Daniel Starke ---
Sure, but it will take some days as I am currently reducing a testcase for
another bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87056
--- Comment #3 from Nathan Sidwell ---
not able to reproduce, (both build using 7.3.0 and bootstrapping)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86684
Segher Boessenkool changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87047
--- Comment #4 from Alexander Monakov ---
This is probably due to logic issue in PR 78120 fix. Its Changelog said,
(noce_process_if_block): Compute an estimate for the original cost when
optimizing for speed, using the minimum
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
Aldy Hernandez changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |aldyh at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
Richard Biener changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86725
--- Comment #4 from rsandifo at gcc dot gnu.org
---
Fixed on trunk so far.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86725
--- Comment #3 from rsandifo at gcc dot gnu.org
---
Author: rsandifo
Date: Wed Aug 22 13:02:48 2018
New Revision: 263774
URL: https://gcc.gnu.org/viewcvs?rev=263774=gcc=rev
Log:
[2/2] Fix bogus inner induction (PR 86725)
This patch is the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86725
--- Comment #2 from rsandifo at gcc dot gnu.org
---
Author: rsandifo
Date: Wed Aug 22 13:02:39 2018
New Revision: 263773
URL: https://gcc.gnu.org/viewcvs?rev=263773=gcc=rev
Log:
[1/2] Fix bogus double reduction (PR 86725)
This patch is the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86964
--- Comment #3 from rguenther at suse dot de ---
On Wed, 22 Aug 2018, znerol at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86964
>
> --- Comment #2 from Joe Lorenz ---
> (In reply to Richard Biener from comment #1)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87038
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86964
--- Comment #2 from Joe Lorenz ---
(In reply to Richard Biener from comment #1)
> Confirmed. Debug info is now more complete. Note
> -feliminate-unused-debug-symbols is only implemented for STABS debugging,
> not for DWARF and from
> my
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87047
--- Comment #3 from Uroš Bizjak ---
(In reply to Andrew Pinski from comment #2)
> I suspect it is treating cost 0 as being free rather than unknown cost. And
> the x86 backend is returning 0 cost for the upper multiple.
There is no truncate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87049
--- Comment #2 from Richard Earnshaw ---
But won't that give problems for C++ because now you'll need to cast the
pointers?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87043
--- Comment #2 from Peter Vitt ---
Oh, I see your point. But then still the question is why this warning is not
shown when compiling with -Og.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=704
--- Comment #15 from Iain Sandoe ---
Author: iains
Date: Wed Aug 22 12:12:46 2018
New Revision: 263768
URL: https://gcc.gnu.org/viewcvs?rev=263768=gcc=rev
Log:
Make the gcc-ar,nm, strip tools respond correctly to --help and --version
when there's
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
--- Comment #3 from Konstantin Kharlamov ---
(In reply to Konstantin Kharlamov from comment #2)
> Thanks, I prefer the `{x}` to just `x` because in the latter I'm being
*"in the former", sorry.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77854
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77854
--- Comment #2 from Jonathan Wakely ---
Author: redi
Date: Wed Aug 22 12:11:17 2018
New Revision: 263767
URL: https://gcc.gnu.org/viewcvs?rev=263767=gcc=rev
Log:
PR libstdc++/77854 document size_type for containers
PR libstdc++/77854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
--- Comment #2 from Konstantin Kharlamov ---
(In reply to Jonathan Wakely from comment #1)
> That would require a lot of special-casing just for std::variant.
Well, I think, in place of std::variant there could be any struct-wrapper; but
I get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87057
--- Comment #1 from Jonathan Wakely ---
(In reply to Konstantin Kharlamov from comment #0)
> When, in a code, a copy-constructor deleted but used, GCC issues an
> absolutely unhelpful message that it couldn't convert the argument. "Why
> can't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87059
Bug ID: 87059
Summary: internal compiler error: in set_value_range, at
tree-vrp.c:289
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87056
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87055
Richard Biener changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898
--- Comment #7 from Jonathan Wakely ---
(In reply to Martin Sebor from comment #2)
> I agree a new warning would be useful. For example, the following code should
> be diagnosed:
>
> struct S { S () throw () { throw 0; } };
This is still
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=4898
--- Comment #6 from Jonathan Wakely ---
Yes, but IMHO it would be a huge waste of time to add a ton of new machinery to
the compiler to check for "correct" usage of an obsolete feature. Most C++98
code didn't even use them, because they were not
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85597
Richard Biener changed:
What|Removed |Added
CC||yates at cscs dot ch
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87046
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87013
Alexandre Oliva changed:
What|Removed |Added
Status|WAITING |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81033
--- Comment #45 from Iain Sandoe ---
Author: iains
Date: Wed Aug 22 11:37:02 2018
New Revision: 263763
URL: https://gcc.gnu.org/viewcvs?rev=263763=gcc=rev
Log:
Fix FDE labels for Darwin
gcc/
PR bootstrap/81033
PR target/81733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52795
--- Comment #10 from Iain Sandoe ---
Author: iains
Date: Wed Aug 22 11:37:02 2018
New Revision: 263763
URL: https://gcc.gnu.org/viewcvs?rev=263763=gcc=rev
Log:
Fix FDE labels for Darwin
gcc/
PR bootstrap/81033
PR target/81733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81733
--- Comment #18 from Iain Sandoe ---
Author: iains
Date: Wed Aug 22 11:37:02 2018
New Revision: 263763
URL: https://gcc.gnu.org/viewcvs?rev=263763=gcc=rev
Log:
Fix FDE labels for Darwin
gcc/
PR bootstrap/81033
PR target/81733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87046
--- Comment #3 from Martin Liška ---
Fixed in r259840.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87054
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87033
Segher Boessenkool changed:
What|Removed |Added
Target|powerpc64-linux-gnu-*, |powerpc*-*-*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87049
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87048
Richard Biener changed:
What|Removed |Added
Target||armeb
--- Comment #1 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87047
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*, i?86-*-*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86988
--- Comment #2 from Richard Biener ---
Author: rguenth
Date: Wed Aug 22 11:01:58 2018
New Revision: 263762
URL: https://gcc.gnu.org/viewcvs?rev=263762=gcc=rev
Log:
2018-08-22 Richard Biener
PR tree-optimization/86988
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87046
Richard Biener changed:
What|Removed |Added
Keywords||needs-bisection
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87043
--- Comment #1 from Richard Biener ---
In .original I see
if (world_rank == 0)
{
...
stat.0 = 0;
error_messages.data = (void * restrict) __builtin_malloc
(MAX_EXPR );
if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87042
Richard Biener changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87041
Richard Biener changed:
What|Removed |Added
Keywords||diagnostic
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87039
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |8.3
1 - 100 of 161 matches
Mail list logo
