https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91614
--- Comment #2 from Bernd Edlinger ---
In some configs the function saves r4/r5 with strd/ldrd,
I think the dg-final statments should ignore register spills,
they are easy to detect since they always use the sp register.
This changed a bit,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91628
Florian Weimer changed:
What|Removed |Added
CC||fw at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65364
--- Comment #7 from Iain Sandoe ---
Author: iains
Date: Sat Aug 31 19:23:54 2019
New Revision: 275248
URL: https://gcc.gnu.org/viewcvs?rev=275248=gcc=rev
Log:
[Darwin, testsuite] Fix PR 65364 (uninit-19.c).
This test currently fails on Darwin,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61250
--- Comment #27 from Iain Sandoe ---
Author: iains
Date: Sat Aug 31 19:12:10 2019
New Revision: 275246
URL: https://gcc.gnu.org/viewcvs?rev=275246=gcc=rev
Log:
[c-family] Backport fix for PCH / PR61250.
When we are parsing a source file, the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82738
Bug 82738 depends on bug 89794, which changed state.
Bug 89794 Summary: combine incorrectly forwards register value through auto-inc
operation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89794
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89794
Segher Boessenkool changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91481
--- Comment #17 from Segher Boessenkool ---
Author: segher
Date: Sat Aug 31 19:01:52 2019
New Revision: 275245
URL: https://gcc.gnu.org/viewcvs?rev=275245=gcc=rev
Log:
rs6000: Fix darn-3.c for GCC 8 and GCC 7
Apparently I didn't properly test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91481
--- Comment #16 from Segher Boessenkool ---
Author: segher
Date: Sat Aug 31 18:58:04 2019
New Revision: 275244
URL: https://gcc.gnu.org/viewcvs?rev=275244=gcc=rev
Log:
rs6000: Fix darn-3.c for GCC 8 and GCC 7
Apparently I didn't properly test
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91607
--- Comment #6 from Marek Polacek ---
That's why I haven't closed the PR.
Trunk seems to emit a potentially bogus error, reducing that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91323
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91629
Bug ID: 91629
Summary: gcc-ar assumes that GCC_EXEC_PREFIX is ${bindir}, but
it is ${libdir}/gcc
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91607
--- Comment #5 from Hannes Hauswedell ---
> (In reply to Marek Polacek from comment #4)
> The ICE was fixed by r266816.
But not for GCC9?
I can confirm that GCC 9.2.1 snapshot from 20190817 still triggers the bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91626
--- Comment #2 from dave.anglin at bell dot net ---
On 2019-08-31 12:10 p.m., marxin at gcc dot gnu.org wrote:
> Can you please bisect that what caused the regression?
>From test results, revision 263930 was okay. Test failed in revision 264295.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91628
Carlos O'Donell changed:
What|Removed |Added
CC||carlos at redhat dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91570
--- Comment #2 from Martin Liška ---
One more test-case with a bit different backtrace:
$ cat ice.i
int a;
int fprintf(int *, char *, ...);
char *strcat();
char *strrchr();
void store_sif(outname, src, offset, incr, height) char *outname;
char
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91627
--- Comment #1 from John David Anglin ---
-bash-4.4$ cat /test/gnu/gcc/gcc/gcc/testsuite/gcc.dg/lto/20081201-2_0.c
/* { dg-lto-options {{-O3 -flto -flto-partition=1to1}} } */
/* Test that cross-TU inlining works. */
extern void abort ();
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91628
Bug ID: 91628
Summary: libdruntime uses glibc internal symbol on s390
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91627
Bug ID: 91627
Summary: FAIL: gcc.dg/lto/20081201-2
c_lto_20081201-2_0.o-c_lto_20081201-2_1.o execute -O3
-flto -flto-partition=1to1
Product: gcc
Version: 10.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91626
Martin Liška changed:
What|Removed |Added
Keywords||needs-bisection
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91623
--- Comment #3 from Jakub Jelinek ---
--- gcc/optabs.c.jj 2019-08-27 12:26:37.392912813 +0200
+++ gcc/optabs.c2019-08-31 18:00:59.838412487 +0200
@@ -5868,6 +5868,8 @@ expand_vec_cond_expr (tree vec_cond_type
icode =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91626
Bug ID: 91626
Summary: FAIL: gcc.dg/lto/pr48622
c_lto_pr48622_0.o-c_lto_pr48622_0.o link, -O -flto
-finline-small-functions -fno-early-inlining
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91625
Bug ID: 91625
Summary: FAIL: gcc.dg/strlenopt-68.c execution test
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91617
--- Comment #3 from Ian Lance Taylor ---
To see how to run libgo tests, see the Debugging section in libgo/README.
The problem you are having with runtime.osinit looks related to a recent libgo
patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91624
Bug ID: 91624
Summary: FAIL: gcc.dg/tree-ssa/sra-18.c scan-tree-dump-times
esra
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91620
--- Comment #2 from frankhb1989 at gmail dot com ---
I missed `unique` should be also affected. The fixes have been applied in
libc++ in the same commit to fix `remove_if`.
MSVC's current implementations are also correct, with a different
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91623
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91622
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38175
Bradly changed:
What|Removed |Added
CC||bradley2844maximus at gmx dot
com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91623
Marc Glisse changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91623
Bug ID: 91623
Summary: [7/8/9 Regression] -msse4.1 -O3 segfault in
/usr/lib/gcc/x86_64-pc-linux-gnu/8.3.0/include/smmintr
in.h:270:10
Product: gcc
Version: 9.2.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91616
--- Comment #1 from Mikael Pettersson ---
Please provide a self-contained test case with a built-in check of its
correctness, or at least a printout of the computed array. I did the latter
locally, and data_array[] looks correct to me (it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91602
--- Comment #7 from Serge Belyshev ---
(In reply to Jim Wilson from comment #5)
> When you build packages separately, each package after the first uses
> feature tests to configure itself appropriately to use the earlier packages.
> When you
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91612
Bernd Edlinger changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91617
--- Comment #2 from Jakub Jelinek ---
Or something is wrong in the go FE langhooks.
Anyway, I have no idea how to debug this, the libgo libgo.log doesn't contain
anything that would make it clear how to run the tests and even looking at the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91552
kargl at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4
CC|
35 matches
Mail list logo
