https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83918
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83918
--- Comment #3 from Jakub Jelinek ---
Author: jakub
Date: Tue Jan 23 07:46:05 2018
New Revision: 256972
URL: https://gcc.gnu.org/viewcvs?rev=256972=gcc=rev
Log:
PR c++/83918
* tree.c (maybe_wrap_with_location): Use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83987
Bug ID: 83987
Summary: [6/7/8 Regression] ICE with OpenMP, sanitizer and
virtual bases
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords:
On Tue, Jan 23, 2018 at 5:49 AM, Ian Lance Taylor wrote:
> On Sun, Jan 21, 2018 at 3:13 PM, Uros Bizjak wrote:
>>
>> The default "go build" compile options over-optimize the auxiliary
>> executable, built in TestCrashDumpsAllThreads testcase
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83190
Leslie Zhai changed:
What|Removed |Added
CC||lesliezhai at llvm dot org.cn
--- Comment
Dear Paul,
The test suite passed without new regression with both -m32 and -m64.
Thanks for the work,
Dominique
I'm heading out of town for a meeting at the end of
week, so gfortran patches/reviews are on hold at the
moment. If someone else wants to step up to review
the patch, I won't object.
--
steve
On Mon, Jan 22, 2018 at 08:29:41PM -0800, Damian Rouson wrote:
> Is Fortran 2018 teams patch ok for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71304
Leslie Zhai changed:
What|Removed |Added
CC||lesliezhai at llvm dot org.cn
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83821
Leslie Zhai changed:
What|Removed |Added
CC||lesliezhai at llvm dot org.cn
--- Comment
On Sun, Jan 21, 2018 at 3:13 PM, Uros Bizjak wrote:
>
> The default "go build" compile options over-optimize the auxiliary
> executable, built in TestCrashDumpsAllThreads testcase
> (libgo/go/runtime/crash_unix_test.go). This over-optimization results
> in removal of the
This patch by Tony Reix adds buildid support to the go tool for AIX.
This supports caching of build results. Bootstrapped and ran Go
testsuite on x86_64-pc-linux-gnu. Committed to mainline.
Ian
Index: gcc/go/gofrontend/MERGE
===
Is Fortran 2018 teams patch ok for trunk?
Damian
On January 19, 2018 at 2:47:39 PM, Alessandro Fanfarillo (elfa...@ucar.edu)
wrote:
I can confirm that the little change suggested by Steve passes the
regtests (on x86_64-pc-linux-gnu) and the regular tests using
OpenCoarrays.
On Fri,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83986
Bug ID: 83986
Summary: [8 Regression] ICE in maybe_record_trace_start, at
dwarf2cfi.c:2348
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81616
--- Comment #50 from Andrew Roberts ---
with the matrix.c benchmark on Ryzen and looking at the other options when
using -march=znver1 and -mtune=znver1
mult took 225281 clocks -march=znver1 -mtune=znver1 -mprefer-vector-width=128
mult took
On 01/22/2018 12:24 PM, Thomas Koenig wrote:
> Am 22.01.2018 um 20:59 schrieb Janne Blomqvist:
>> On Mon, Jan 22, 2018 at 9:12 PM, Paul Richard Thomas
>> wrote:
>>> This patch has been triggered by Thomas's recent message to the list.
>>> Not only did I start work
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83496
--- Comment #11 from Paul Hua ---
>
> Actually, I think that assembly looks unaffected by the issue.
>
Right.
> I have some doubts about the commits mentioned in this thread as well.
> r240965 looks like it simply changes the code generator
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83985
Bug ID: 83985
Summary: Compile time hog for 32-bit BE powerpc targets
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: compile-time-hog
Severity: normal
On Mon, Jan 22, 2018 at 6:14 PM, Jakub Jelinek wrote:
> On Mon, Jan 22, 2018 at 04:49:34PM -0500, Jason Merrill wrote:
>> On Thu, Jan 18, 2018 at 6:13 PM, Jakub Jelinek wrote:
>> > Before location wrappers were introduced, the
>> >
Sent from my iPhone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83984
Bug ID: 83984
Summary: ld: The value 0x80005 does not fit when
applying the relocation DIR21L
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
David Malcolm changed:
What|Removed |Added
Keywords||ice-on-valid-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83660
--- Comment #6 from kelvin at gcc dot gnu.org ---
For what it's worth, I reconfigured my build with --enable-checking=yes,tree in
hopes that this would help us find the C++ parser code that is responsible for
creating the problematic syntax tree.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83982
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
--- Comment #2 from Jonathan Wakely ---
https://wg21.link/lwg2033 changed the requirements.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83983
Bug ID: 83983
Summary: FAIL: g++.dg/lto/pr83121 (test for LTO warnings,
pr83121_0.C line 8)
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
Jonathan Wakely changed:
What|Removed |Added
Keywords||rejects-valid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83589
--- Comment #8 from Tom de Vries ---
Created attachment 43209
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43209=edit
Patch inserting fake_nop only in case of branch-around-nothing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83980
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
---
Hi!
On Mon, Jan 22, 2018 at 10:57:35AM +0100, Martin Jambor wrote:
> On Fri, Jan 19 2018, Sandra Loosemore wrote:
> > On 01/19/2018 10:14 AM, Jeff Law wrote:
> >
> >> cc0 needs to die. That doesn't mean that any particular target needs to
> >> be dropped -- it just means that someone has to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83982
Bug ID: 83982
Summary: Exception guarantee of C++14 vector::resize(size_type)
is not met
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83981
Bug ID: 83981
Summary: vector::resize(size_type) should not require T to be
CopyInsertable when std=c++14
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
On Mon, Jan 22, 2018 at 12:32:13PM -0600, Segher Boessenkool wrote:
> Hi Mike,
>
> If it is needed on the branches, okay for there too (once 7 reopens).
It is needed on GCC 7 if you compile the test for -mcpu=power9 and use
an explicit __float128 instead of long double (-mabi=ieeelongdouble is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83957
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83081
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Mon, Jan 22, 2018 at 04:49:34PM -0500, Jason Merrill wrote:
> On Thu, Jan 18, 2018 at 6:13 PM, Jakub Jelinek wrote:
> > Before location wrappers were introduced, the
> > potential_constant_expression_1
> > assumption that a VIEW_CONVERT_EXPR must have non-NULL type was
Hi!
I've recently added the complete_type call in case the structured binding
is a reference to a type that needs to be instantiated.
This testcase shows a problem where it can't be instantiated and we ICE
because we don't expect an incomplete type. If decl isn't a reference,
cp_finish_decl for
Hi!
The ompexpssa pass will do TODO_update_ssa_only_virtuals, so don't need
to handle in detail vops. In this case the inner_phi is NULL for the vop
and we crash on it.
Bootstrapped/regtested on x86_64-linux and i686-linux, committed to trunk.
2018-01-22 Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83081
--- Comment #11 from Jakub Jelinek ---
Author: jakub
Date: Mon Jan 22 22:59:33 2018
New Revision: 256966
URL: https://gcc.gnu.org/viewcvs?rev=256966=gcc=rev
Log:
PR tree-optimization/83081
* profile-count.h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83957
--- Comment #4 from Jakub Jelinek ---
Author: jakub
Date: Mon Jan 22 23:00:50 2018
New Revision: 256967
URL: https://gcc.gnu.org/viewcvs?rev=256967=gcc=rev
Log:
PR tree-optimization/83957
* omp-expand.c (expand_omp_for_generic):
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83720
--- Comment #4 from Jason Merrill ---
Author: jason
Date: Mon Jan 22 22:41:48 2018
New Revision: 256965
URL: https://gcc.gnu.org/viewcvs?rev=256965=gcc=rev
Log:
PR c++/83720 - different fix
* decl2.c (determine_visibility): Fix
In this testcase, determine_visibility was relying on the template
argument handling to constrain the lambda in h to internal linkage.
In the new lambda model, the local lambda has no template info, so
that was breaking. So we shouldn't rely on the decl itself to trigger
checking the containing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83980
Bug ID: 83980
Summary: Various issues with character length in array
constructors
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
On Mon, Jan 22, 2018 at 09:59:41PM +0200, Janne Blomqvist wrote:
> On Mon, Jan 22, 2018 at 9:12 PM, Paul Richard Thomas
> wrote:
> > This patch has been triggered by Thomas's recent message to the list.
> > Not only did I start work late relative to stage 3 but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83979
rsandifo at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
Hi again,
On 22/01/2018 22:50, Paolo Carlini wrote:
Ok. The below passes the C++ testsuite and I'm finishing testing it.
Therefore, as you already hinted to, we can now say that what was
*really* missing from potential_constant_expression_1 was the use of
default_init_uninitialized_part,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83515
--- Comment #2 from DIL ---
For GFORTRAN 6.4.0 and earlier, the relevant compiler bug has been fixed in
78300.
Hi,
On 22/01/2018 16:52, Jason Merrill wrote:
Thus the below, carefully tested over the we, would be a change completely
removing the problematic error_at call, plus some testcases checking that we
would still do the right thing in a few cases (bug submitter added
constexpr-83921-2.C). The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83979
David Malcolm changed:
What|Removed |Added
CC||rsandifo at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83976
Harald Anlauf changed:
What|Removed |Added
CC||anlauf at gmx dot de
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83720
--- Comment #3 from Jason Merrill ---
Author: jason
Date: Mon Jan 22 21:51:53 2018
New Revision: 256964
URL: https://gcc.gnu.org/viewcvs?rev=256964=gcc=rev
Log:
PR c++/83720 - ICE with lambda and LTO.
* decl2.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83979
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Thu, Jan 18, 2018 at 6:13 PM, Jakub Jelinek wrote:
> Before location wrappers were introduced, the potential_constant_expression_1
> assumption that a VIEW_CONVERT_EXPR must have non-NULL type was right,
> if it is a type dependent reinterpret cast, it would be
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83974
David Malcolm changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Mon, 22 Jan 2018, Sebastian Huber wrote:
>> +GCC 7.3
>> +
>> +This is the > href="https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVEDresolution=FIXEDtarget_milestone=7.3;>list
>> +of problem reports (PRs) from GCC's bug tracking system that are
>> +known to be fixed in the 7.3 release.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83979
Bug ID: 83979
Summary: [8 Regression] ICE with pointer comparison
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69452
--- Comment #7 from David Malcolm ---
Author: dmalcolm
Date: Mon Jan 22 20:53:57 2018
New Revision: 256963
URL: https://gcc.gnu.org/viewcvs?rev=256963=gcc=rev
Log:
Finish removing class move_computations_dom_walker
r232820 (aka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83967
--- Comment #3 from rguenther at suse dot de ---
On January 22, 2018 4:36:00 PM GMT+01:00, "pinskia at gcc dot gnu.org"
wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83967
>
>--- Comment #2 from Andrew Pinski
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
--- Comment #5 from Michael Meissner ---
On Mon, Jan 22, 2018 at 08:13:11PM +, segher at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
>
> --- Comment #2 from Segher Boessenkool ---
> Where do you get TImode
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
--- Comment #4 from Michael Meissner ---
On Mon, Jan 22, 2018 at 08:13:11PM +, segher at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
>
> --- Comment #2 from Segher Boessenkool ---
> Where do you get TImode
On January 22, 2018 8:50:44 PM GMT+01:00, David Malcolm
wrote:
>r232820 (aka 2c7b2f8860794cc9b9cf5eeea9d7dc109c0de3be) removed the
>implementation of class move_computations_dom_walker, but kept the
>decl.
>
>This patch removes the stray decl.
>
>Successfully bootstrapped on
Am 22.01.2018 um 20:59 schrieb Janne Blomqvist:
On Mon, Jan 22, 2018 at 9:12 PM, Paul Richard Thomas
wrote:
This patch has been triggered by Thomas's recent message to the list.
Not only did I start work late relative to stage 3 but debugging took
somewhat longer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
--- Comment #3 from Jakub Jelinek ---
Apparently vectorization, from expand dump it looks like TImode is mode of
vector(2) long long int.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
--- Comment #2 from Segher Boessenkool ---
Where do you get TImode with this testcase?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83969
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
On Fri, 2018-01-19 at 09:45 +0100, Richard Biener wrote:
> On Fri, Jan 19, 2018 at 12:36 AM, David Malcolm
> wrote:
> > PR tree-optimization/83510 reports that r255649 (for
> > PR tree-optimization/83312) introduced a false positive for
> > -Warray-bounds for array accesses
On Mon, Jan 22, 2018 at 9:12 PM, Paul Richard Thomas
wrote:
> This patch has been triggered by Thomas's recent message to the list.
> Not only did I start work late relative to stage 3 but debugging took
> somewhat longer than anticipated. Therefore, to get this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81616
--- Comment #49 from Jan Hubicka ---
> matrix.c is still needing additional options to get the best out of the Ryzen
> processor. But is better than before (223029 clocks vs 371978 originally),
> but 122677 is achievable with the right options.
Dne 2018-01-22 19:36, Jakub Jelinek napsal:
On Mon, Jan 22, 2018 at 06:44:17PM +0100, Jan Hubicka wrote:
> + /* Split *THIS (ORIG) probability into 2 probabilities, such that
> + the returned one (FIRST) is *THIS * CPROB and *THIS is
> + adjusted (SECOND) so that FIRST + FIRST.invert
This patch adds a few extra assertions to selftest::test_location_wrappers.
Successfully bootstrapped on x86_64-pc-linux-gnu.
OK for trunk?
gcc/ChangeLog:
* tree.c (selftest::test_location_wrappers): Add more test
coverage.
---
gcc/tree.c | 10 ++
1 file changed, 10
"make selftest-valgrind" shows a few leaks in sbitmap.c's selftests;
this patch fixes them.
Successfully bootstrapped on x86_64-pc-linux-gnu.
OK for trunk?
gcc/ChangeLog:
* sbitmap.c (selftest::test_set_range): Fix memory leaks.
(selftest::test_bit_in_range): Likewise.
---
r232820 (aka 2c7b2f8860794cc9b9cf5eeea9d7dc109c0de3be) removed the
implementation of class move_computations_dom_walker, but kept the decl.
This patch removes the stray decl.
Successfully bootstrapped on x86_64-pc-linux-gnu.
OK for trunk?
gcc/ChangeLog:
PR tree-optimization/69452
Hi,
On Fri, 12 Jan 2018, Joseph Myers wrote:
> On Fri, 12 Jan 2018, Alexander Monakov wrote:
>
> > No. The qsort_chk effort was limited to catching instances where comparators
> > are invalid, i.e. lack anti-commutativity (may indicate A < B < A) or
> > transitivity property (may indicate A < B
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83862
--- Comment #2 from Michael Meissner ---
Author: meissner
Date: Mon Jan 22 19:36:18 2018
New Revision: 256959
URL: https://gcc.gnu.org/viewcvs?rev=256959=gcc=rev
Log:
[gcc]
2018-01-22 Michael Meissner
PR
On Mon, Jan 22, 2018 at 12:32:13PM -0600, Segher Boessenkool wrote:
> Hi Mike,
>
> Thanks for doing this!
>
> On Sun, Jan 21, 2018 at 07:03:58PM -0500, Michael Meissner wrote:
> > With these patches, the generator code issues an UNSPEC (signbit2_dm)
> > just to get the high double word, and the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83978
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82882
--- Comment #6 from Jakub Jelinek ---
*** Bug 83978 has been marked as a duplicate of this bug. ***
This patch has been triggered by Thomas's recent message to the list.
Not only did I start work late relative to stage 3 but debugging took
somewhat longer than anticipated. Therefore, to get this committed
asap, we will have to beg the indulgence of the release managers and
prompt review and/or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83879
--- Comment #5 from Nathan Sidwell ---
usage is --dynamic-list=file-name, which would be a little awkward.
--dynamic-list-data is probably more useable and available.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83879
--- Comment #4 from Marco Castelluccio ---
Would it be feasible to force exporting "__gcov_master" to the dynamic symbol
table when coverage instrumentation is enabled?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83978
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83978
Bug ID: 83978
Summary: [8 Regression] ICE in determine_visibility
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81616
--- Comment #48 from Andrew Roberts ---
Correction, that should be 23 not 23000 for the haswell drop in
performance.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81616
--- Comment #47 from Andrew Roberts ---
Again with the latest snapshot:
gcc version 8.0.1 20180121
matrix.c is still needing additional options to get the best out of the Ryzen
processor. But is better than before (223029 clocks vs 371978
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83935
--- Comment #4 from Pierre-Marie de Rodat ---
(In reply to Tom Tromey from comment #3)
> TBH this did not make sense to me, either, which is partly why I originally
> wrote my patch the "more natural" way -- then this got caught in review,
> see
On Mon, Jan 22, 2018 at 06:44:17PM +0100, Jan Hubicka wrote:
> > + /* Split *THIS (ORIG) probability into 2 probabilities, such that
> > + the returned one (FIRST) is *THIS * CPROB and *THIS is
> > + adjusted (SECOND) so that FIRST + FIRST.invert () * SECOND
> > + == ORIG. */
>
> To
Hi Mike,
Thanks for doing this!
On Sun, Jan 21, 2018 at 07:03:58PM -0500, Michael Meissner wrote:
> I've reworked the patch for PR83864. This bug is due to the compiler issuing
> an internal error for code of the form on a little endian system:
>
> int sb (_Float128 *p, unsigned long n) {
* Manuel Rigger:
> Details: We downloaded all C projects from GitHub that had more than 80
> GitHub stars, which yielded almost 5,000 projects with a total of more
> than one billion lines of C code. We filtered GCC, forks of GCC, and
> other compilers as we did not want to incorporate internal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81616
--- Comment #46 from Andrew Roberts ---
With the latest snapshot:
gcc version 8.0.1 20180121
For the mt19937ar things now look reasonable without any strange options on
Ryzen.
Top 5
mt19937ar took 226849 clocks -march=amdfam10 -mtune=btver2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83758
David Edelsohn changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83977
Bug ID: 83977
Summary: [8 Regression] ICE in simd_clone_clauses_extract, at
omp-simd-clone.c:184
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83976
--- Comment #1 from G. Steinmetz ---
This variant works as expected :
$ cat z2.f90
program p
type t
integer :: a
end type
class(t), allocatable :: x
type(t) :: z = t(3)
x = z
z = x
print *, z
end
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83976
Bug ID: 83976
Summary: ICE in gfc_add_component_ref, at fortran/class.c:211
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
--- Comment #1 from G. Steinmetz ---
Configured with --enable-checking=yes :
$ gfortran-8-20180121-chk -c z1.f90
z1.f90:1:0:
subroutine s(x)
internal compiler error: tree check: expected parm_decl, have var_decl in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83975
Bug ID: 83975
Summary: [8 Regression] ICE in set_parm_default_def_partition,
at tree-ssa-coalesce.c:1919
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Hi -
> Problems are still occurring for me; Bugzilla gives me 504 Gateway
> Time-outs when I try to access it tonight...
OK, we reworked some of the database routine maintenance workload,
e.g., a nightly cleanup pass that was quite likely excessive, and
will keep monitoring.
- FChE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67804
G. Steinmetz changed:
What|Removed |Added
CC||gs...@t-online.de
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83974
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
1 - 100 of 253 matches
Mail list logo