rop -c hyr6b31a.c
during GIMPLE pass: fre
hyr6b31a.c: In function 'tp':
hyr6b31a.c:22:1: internal compiler error: in do_rpo_vn, at
tree-ssa-sccvn.c:6566
22 | }
| ^
0x6a712b do_rpo_vn
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180916/work/gcc-9-20180916/gcc/tree-ssa-sccvn.c:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87327
Bug ID: 87327
Summary: Calling member functions on captured constexpr
variables "is not a constant expression"
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87322
ensadc at mailnesia dot com changed:
What|Removed |Added
CC||ensadc at mailnesia dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666
Hans-Peter Nilsson changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87317
--- Comment #5 from H.J. Lu ---
Created attachment 44702
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44702&action=edit
A patch
Please try this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666
--- Comment #15 from Hans-Peter Nilsson ---
Author: hp
Date: Sun Sep 16 21:23:36 2018
New Revision: 264351
URL: https://gcc.gnu.org/viewcvs?rev=264351&root=gcc&view=rev
Log:
PR target/85666
* config/mmix/mmix.c (mmix_assemble_int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87318
--- Comment #5 from Jerry DeLisle ---
(In reply to janus from comment #4)
> (In reply to Jerry DeLisle from comment #3)
> > Created attachment 44700 [details]
> > Revised dtio_1.f90
> >
> > Will this attached version suffice?
>
> Looks good at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87318
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #3)
> Created attachment 44700 [details]
> Revised dtio_1.f90
>
> Will this attached version suffice?
Looks good at first sight. Will try ifort 19 on it soo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84543
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86484
janus at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86484
--- Comment #7 from janus at gcc dot gnu.org ---
Fixed on 9-trunk with r264350. Closing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87326
Bug ID: 87326
Summary: Support the NEW_INDEX= specifier in the FORM TEAM
statement
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37802
Thomas Koenig changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27766
Bug 27766 depends on bug 37802, which changed state.
Bug 37802 Summary: Improve wording for matmul bound checking
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37802
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86484
--- Comment #6 from janus at gcc dot gnu.org ---
Author: janus
Date: Sun Sep 16 19:57:52 2018
New Revision: 264350
URL: https://gcc.gnu.org/viewcvs?rev=264350&root=gcc&view=rev
Log:
fix PR 86484 and PR 84543
2018-09-16 Janus Weil
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84543
--- Comment #2 from janus at gcc dot gnu.org ---
Author: janus
Date: Sun Sep 16 19:57:52 2018
New Revision: 264350
URL: https://gcc.gnu.org/viewcvs?rev=264350&root=gcc&view=rev
Log:
fix PR 86484 and PR 84543
2018-09-16 Janus Weil
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84543
janus at gcc dot gnu.org changed:
What|Removed |Added
Keywords||link-failure
Statu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86484
janus at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37802
--- Comment #4 from Thomas Koenig ---
Author: tkoenig
Date: Sun Sep 16 19:37:44 2018
New Revision: 264349
URL: https://gcc.gnu.org/viewcvs?rev=264349&root=gcc&view=rev
Log:
2018-09-16 Thomas Koenig
PR fortran/37802
* frontend
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52952
--- Comment #51 from Manuel López-Ibáñez ---
There are few things still that don't work:
1. C++ does not work
2. Locations within strings expanded from a macro
3. Location within strings from a const char array.
void foo(void) {
#define c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85948
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62181
Manuel López-Ibáñez changed:
What|Removed |Added
CC||vittorio.romeo at outlook dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78679
Manuel López-Ibáñez changed:
What|Removed |Added
Status|NEW |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62181
Manuel López-Ibáñez changed:
What|Removed |Added
CC||veksler at il dot ibm.com
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49481
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43789
Manuel López-Ibáñez changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78081
Manuel López-Ibáñez changed:
What|Removed |Added
Last reconfirmed|2017-04-28 00:00:00 |2018-9-16
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78915
Manuel López-Ibáñez changed:
What|Removed |Added
CC||manu at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63418
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 63418, which changed state.
Bug 63418 Summary: false positive with -Wmaybe-uninitialized
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63418
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49754
Manuel López-Ibáñez changed:
What|Removed |Added
CC||matt at use dot net
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 42561, which changed state.
Bug 42561 Summary: missing uninitialized variable warning on simple arrays
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42561
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42561
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #11 from Marc Glisse ---
Trunk doesn't show the warning (gcc-8 does).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34515
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33933
Manuel López-Ibáñez changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26492
Manuel López-Ibáñez changed:
What|Removed |Added
Target|i486-linux-gnu |
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
Manuel López-Ibáñez changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71157
--- Comment #9 from Paul Eggert ---
(In reply to Eric Gallager from comment #8)
> Try marking it up with __attribute__((returns_nonnull)) and/or
> __attribute__((nonnull)). If the first one works, then it's a case where GCC
> should suggest it,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85954
--- Comment #6 from Paul Thomas ---
Created attachment 44701
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44701&action=edit
A fix for the PR
This regtests OK.
It needs one or two further tweaks before submission, which will occur
tomorr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87325
Bug ID: 87325
Summary: determine_base_object does not consider consider
address space of base expr
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: norma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86551
--- Comment #4 from janus at gcc dot gnu.org ---
The patch in comment #3 shows lots of regressions in the testsuite, but this
one should be better:
diff --git a/gcc/fortran/match.c b/gcc/fortran/match.c
index 85247dd8334..6cf816be511 100644
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86470
--- Comment #3 from janus at gcc dot gnu.org ---
On current trunk I get the following backtrace:
internal compiler error: Segmentation fault
0xc71fdf crash_signal
/home/jweil/github/gcc/trunk/gcc/toplev.c:325
0x948110 contains_struct_che
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86470
janus at gcc dot gnu.org changed:
What|Removed |Added
CC||janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
--- Comment #64 from John Paul Adrian Glaubitz ---
FYI, I am setting up a PowerPCSPE porterbox the next days and hope to get it
added to the gcc compile farm as a test machine. So any patches can be tested
there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87093
--- Comment #8 from Tony E Lewis ---
Yep - verified on the GCC trunk on Godbolt ("9.0.0 20180915 (experimental)").
Fantastic stuff. Thanks very much Ville.
46 matches
Mail list logo