[Bug ipa/67783] quadratic time consumption in IPA inlining with -O1 and higher

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67783 Richard Biener changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned

[Bug libgcc/67792] GCC 5.2 - make clean fails in libgcc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67792 --- Comment #1 from Andreas Schwab --- Nobody is testing make clean, patches welcome. It's much easier to just remove the build directory before starting over.

[Bug tree-optimization/67794] [6 regression] internal compiler error: Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67794 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #4 from Bernd Edlinger --- necessary compiler options to trigger the ICE: -O2 and -mapcs arm-linux-gnueabihf-gcc -O2 -mapcs -S kernel-ice.c

[Bug target/51726] LTO and attribute 'selectany'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51726 Richard Biener changed: What|Removed |Added Known to fail|4.10.0 |5.0 --- Comment #7 from Richard Biener

[Bug ipa/67783] quadratic time consumption in IPA inlining with -O1 and higher

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67783 Richard Biener changed: What|Removed |Added Keywords||compile-time-hog

[Bug ipa/67783] quadratic time consumption in IPA inlining with -O1 and higher

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67783 --- Comment #2 from Richard Biener --- I believe we should greatly simplify this heuristic to only consider loop header PHI defs as IVs where we derive predicates for the stride for: Index: gcc/ipa-inline-analysis.c

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 Markus Trippelsdorf changed: What|Removed |Added CC||trippels at gcc dot gnu.org ---

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #9 from ktkachov at gcc dot gnu.org --- (In reply to Bernd Edlinger from comment #7) > (In reply to ktkachov from comment #6) > > Perhaps a bisection to the revision that started this could shed some light > > absolutely, but my

[Bug go/66870] split stack issues on ppc64le and ppc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870 --- Comment #25 from boger at us dot ibm.com --- (In reply to Andreas Schwab from comment #24) > ../../gcc/go/gospec.c: In function 'void > lang_specific_driver(cl_decoded_option**, unsigned int*, int*)': > ../../gcc/go/gospec.c:161:7: error:

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #6 from ktkachov at gcc dot gnu.org --- Perhaps a bisection to the revision that started this could shed some light

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 --- Comment #3 from frankhb1989 at gmail dot com --- (In reply to Markus Trippelsdorf from comment #1) > gcc even warns: > > t.cpp: In function ‘std::experimental::fundamentals_v1::string_view& > erase_left(size_t,

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 Bernd Edlinger changed: What|Removed |Added CC||vmakarov at redhat dot com --- Comment

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 frankhb1989 at gmail dot com changed: What|Removed |Added Version|unknown |5.2.0 --- Comment #6 from

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 Marc Glisse changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Version|5.2.0

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 --- Comment #8 from frankhb1989 at gmail dot com --- (In reply to Markus Trippelsdorf from comment #4) > Return by value if you want to avoid undefined behavior. No. This is not the point. For something like 'std::move' or 'std::forward', can

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #11 from Bernd Edlinger --- I must admit, that I don't know what I am doing here, ... but this (completely untested) patch seems to fix the ICE: (and at least my linux kernel compiles without ICE now) --- lra-assigns.c.jj

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 --- Comment #9 from frankhb1989 at gmail dot com --- (In reply to Richard Biener from comment #5) > I would guess the issue is that ?: returns an rvalue (but that may not be > 100% correct if omitting the cast works and does not warn) In C++ ?:

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 Markus Trippelsdorf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug target/66776] [AArch64] zero-extend version of csel not matching properly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66776 renlin at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #10 from ktkachov at gcc dot gnu.org --- The ICE started with: Author: vmakarov Date: Tue Sep 1 19:37:52 2015 + 2015-09-01 Vladimir Makarov PR

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #7 from Bernd Edlinger --- (In reply to ktkachov from comment #6) > Perhaps a bisection to the revision that started this could shed some light absolutely, but my computer powers are too limited for that. could you help?

[Bug c++/67795] New: Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 Bug ID: 67795 Summary: Wrong code generated for conditional expression with cast Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 frankhb1989 at gmail dot com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug target/54236] [SH] Improve addc and subc insn utilization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54236 --- Comment #18 from Oleg Endo --- Author: olegendo Date: Thu Oct 1 12:36:15 2015 New Revision: 228332 URL: https://gcc.gnu.org/viewcvs?rev=228332=gcc=rev Log: gcc/testsuite/ PR target/54236 * gcc.target/sh/pr54236-6.c: Fix

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 --- Comment #5 from Richard Biener --- I would guess the issue is that ?: returns an rvalue (but that may not be 100% correct if omitting the cast works and does not warn)

[Bug c++/67795] Wrong code generated for conditional expression with cast

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67795 --- Comment #10 from frankhb1989 at gmail dot com --- (In reply to Marc Glisse from comment #7) > Hmm, with the static_cast, the front-end produces: > > < = (struct string_view &) (struct string_view > *) NON_LVALUE_EXPR <(struct string_view &)

[Bug go/66870] split stack issues on ppc64le and ppc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870 --- Comment #26 from Andreas Schwab --- Just try any target.

[Bug rtl-optimization/67786] [6 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67786 --- Comment #3 from ktkachov at gcc dot gnu.org --- Patch posted at: https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00056.html

[Bug c++/67796] New: Definition for custom std::swap found by ADL but not used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67796 Bug ID: 67796 Summary: Definition for custom std::swap found by ADL but not used Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal

[Bug target/59305] [4.9/5/6 Regression] gcc.dg/atomic/c11-atomic-exec-5.c fails with WARNING: program timed out on x86_64-apple-darwin13

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59305 --- Comment #27 from Christophe Lyon --- I've noticed timeouts on aarch64 too, where the hook is implemented IIUC. Run-time varies a lot too: from 5 minutes to ~1h, with the same binary, same machine, where I am the only user.

[Bug fortran/67721] deep copy missing when assigning a derived type constructor to an array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67721 --- Comment #5 from Mikael Morin --- Author: mikael Date: Thu Oct 1 14:01:37 2015 New Revision: 228339 URL: https://gcc.gnu.org/viewcvs?rev=228339=gcc=rev Log: Fix missing deep copy when assigning a DT constructor to an array This adds the

[Bug tree-optimization/67769] [6 Regression] VRP pass does wrong optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67769 --- Comment #4 from Marek Polacek --- Author: mpolacek Date: Thu Oct 1 14:25:42 2015 New Revision: 228341 URL: https://gcc.gnu.org/viewcvs?rev=228341=gcc=rev Log: PR tree-optimization/67769 * tree-ssa-phiopt.c

[Bug go/66870] split stack issues on ppc64le and ppc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870 Ian Lance Taylor changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/67798] Constant shift operation to the openmp unsigned loop variable gives a wrong result .

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67798 Hiroaki Yamanouchi changed: What|Removed |Added Severity|major |normal

[Bug middle-end/67754] [graphite] Many testsuite failures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67754 --- Comment #11 from Sebastian Pop --- Author: spop Date: Thu Oct 1 15:17:51 2015 New Revision: 228346 URL: https://gcc.gnu.org/viewcvs?rev=228346=gcc=rev Log: add recursion on the inner loops We now check that all data references in the

[Bug libgcc/67792] GCC 5.2 - make clean fails in libgcc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67792 --- Comment #3 from Jonathan Wakely --- Probably not fixed, just latent. Everyone just removes the whole build dir, which works far more reliably.

[Bug fortran/67721] deep copy missing when assigning a derived type constructor to an array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67721 --- Comment #6 from Mikael Morin --- Author: mikael Revision: 228170 Modified property: svn:log Modified: svn:log at Thu Oct 1 14:03:32 2015 -- --- svn:log (original)

[Bug target/67797] New: [ARM] Unnecessary r0 saving for memset call

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67797 Bug ID: 67797 Summary: [ARM] Unnecessary r0 saving for memset call Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/67799] The function strtoul and strtoull in do not work correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67799 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/67721] deep copy missing when assigning a derived type constructor to an array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67721 Mikael Morin changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c++/67798] Constant shift operation to the openmp unsigned loop variable gives a wrong result .

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67798 Hiroaki Yamanouchi changed: What|Removed |Added Severity|critical|major

[Bug go/66870] split stack issues on ppc64le and ppc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870 --- Comment #30 from ian at gcc dot gnu.org --- Author: ian Date: Thu Oct 1 14:43:57 2015 New Revision: 228342 URL: https://gcc.gnu.org/viewcvs?rev=228342=gcc=rev Log: PR go/66870 * gospec.c (lang_specific_driver): Only look

[Bug c++/67798] New: Constant shift operation to the openmp unsigned loop variable gives a wrong result .

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67798 Bug ID: 67798 Summary: Constant shift operation to the openmp unsigned loop variable gives a wrong result . Product: gcc Version: 5.2.0 Status: UNCONFIRMED

[Bug c/65345] ICE with _Generic selection on _Atomic int

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65345 --- Comment #14 from Marek Polacek --- Author: mpolacek Date: Thu Oct 1 14:53:10 2015 New Revision: 228343 URL: https://gcc.gnu.org/viewcvs?rev=228343=gcc=rev Log: PR c/65345 * config/i386/i386.c

[Bug c++/67799] New: The function strtoul and strtoull in do not work correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67799 Bug ID: 67799 Summary: The function strtoul and strtoull in do not work correctly Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/67721] deep copy missing when assigning a derived type constructor to an array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67721 --- Comment #4 from Mikael Morin --- (In reply to Dominique d'Humieres from comment #3) > Any plan to back port the fix to 5.3? Yes, Paul suggested it in his approval message. I'm doing it now.

[Bug go/66870] split stack issues on ppc64le and ppc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870 --- Comment #27 from Ian Lance Taylor --- Any target that doesn't have a -m32 option. This does work on x86 targets, since they have a -m32 option in their config/CPU/CPU.opt file. Sorry for not catching this.

[Bug go/66870] split stack issues on ppc64le and ppc64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870 --- Comment #28 from boger at us dot ibm.com --- I could put back the #ifdef TARGET_CAN_SPLIT_STACK_64BIT around the OPT_m32 case if that is OK. Doesn't fail on the builds for ppc64le or ppc64 either.

[Bug c/65345] ICE with _Generic selection on _Atomic int

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65345 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug middle-end/67754] [graphite] Many testsuite failures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67754 --- Comment #12 from Sebastian Pop --- Author: spop Date: Thu Oct 1 15:17:58 2015 New Revision: 228347 URL: https://gcc.gnu.org/viewcvs?rev=228347=gcc=rev Log: call scev analysis in scop-detection as in sese-to-poly Before our rewrite of the

[Bug middle-end/67754] [graphite] Many testsuite failures

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67754 Sebastian Pop changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libgcc/67792] GCC 5.2 - make clean fails in libgcc

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67792 --- Comment #2 from Gary Funck --- (In reply to Andreas Schwab from comment #1) > Nobody is testing make clean, patches welcome. It's much easier to just > remove the build directory before starting over. OK. I don't plan on looking into it.

[Bug c++/67796] Definition for custom std::swap found by ADL but not used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67796 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #14 from Vladimir Makarov --- (In reply to Bernd Edlinger from comment #5) > > My patch from yesterday makes no difference here, but what's funny is, > that the set register was originally r138 but now the dump says > "set

[Bug target/59305] [4.9/5/6 Regression] gcc.dg/atomic/c11-atomic-exec-5.c fails with WARNING: program timed out on x86_64-apple-darwin13

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59305 --- Comment #28 from Andrew Pinski --- (In reply to Christophe Lyon from comment #27) > I've noticed timeouts on aarch64 too, where the hook is implemented IIUC. > > Run-time varies a lot too: from 5 minutes to ~1h, with the same binary, same >

[Bug c++/67799] The function strtoul and strtoull in do not work correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67799 Martin Sebor changed: What|Removed |Added CC||msebor at gcc dot gnu.org --- Comment #5

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #13 from Vladimir Makarov --- (In reply to Bernd Edlinger from comment #11) > I must admit, that I don't know what I am doing here, > ... but this (completely untested) patch seems to fix the ICE: > (and at least my linux kernel

[Bug c++/67799] The function strtoul and strtoull in do not work correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67799 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/67799] The function strtoul and strtoull in do not work correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67799 8826055 at 163 dot com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug c++/67796] Definition for custom std::swap found by ADL but not used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67796 --- Comment #2 from rkirchge at gmail dot com --- Thank you for the quick reply. Defining the swap overload in std does violate the standard, but it is the shortest example that reproduces the behavior I am seeing. In my code, I have defined a

[Bug tree-optimization/67800] New: [6 Regression] Missed vectorization opportunity on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67800 Bug ID: 67800 Summary: [6 Regression] Missed vectorization opportunity on x86 Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 Vladimir Makarov changed: What|Removed |Added CC||vmakarov at gcc dot gnu.org ---

[Bug c++/67796] Definition for custom std::swap found by ADL but not used

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67796 --- Comment #3 from Jonathan Wakely --- This (invalid) program prints "ADL Works!" as expected, so without a proper testcase (as required by https://gcc.gnu.org/bugs/ anyway) we have no idea what your actual code does: #include #include

[Bug tree-optimization/67800] [6 Regression] Missed vectorization opportunity on x86

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67800 --- Comment #1 from Alexander Fomin --- Nota bene: -fPIE -pie options can be ommited.

[Bug libffi/67801] New: error in libffi documentation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67801 Bug ID: 67801 Summary: error in libffi documentation Product: gcc Version: unknown Status: UNCONFIRMED Severity: trivial Priority: P3 Component: libffi

[Bug c++/67799] The function strtoul and strtoull in do not work correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67799 --- Comment #4 from 8826055 at 163 dot com --- (In reply to Jonathan Wakely from comment #3) > (In reply to Jonathan Wakely from comment #1) > > If you look in you will see these functions are not provided by > > GCC's header, they come from

[Bug fortran/67804] New: ICE on data initialization of type(character) with wrong data

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67804 Bug ID: 67804 Summary: ICE on data initialization of type(character) with wrong data Product: gcc Version: 5.2.1 Status: UNCONFIRMED Severity: normal

[Bug target/67756] [6 Regression] ICE compiling Linux Kernel fs/namei.c on ARM

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67756 --- Comment #15 from Bernd Edlinger --- (In reply to Vladimir Makarov from comment #14) > (In reply to Bernd Edlinger from comment #5) > > > > > My patch from yesterday makes no difference here, but what's funny is, > > that the set register

[Bug target/67688] [MinGW/Cygwin] Attributes selectany and section cannot be used together

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67688 Kai Tietz changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|

[Bug fortran/67802] New: ICE on initializing character with wrong len type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67802 Bug ID: 67802 Summary: ICE on initializing character with wrong len type Product: gcc Version: 5.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug libffi/67801] error in libffi documentation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67801 --- Comment #1 from Andrew Pinski --- Also varabi too. that is "var{abi}".

[Bug fortran/67805] ICE on array constructor with wrong character specification

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67805 --- Comment #2 from Gerhard Steinmetz --- And these variants are silently accepted : $ cat z5.f90 program p print *, '1: ', [character(.true.) :: 'x', 'y'] print *, '2: ', [character(.false.) ::

[Bug tree-optimization/67769] [6 Regression] VRP pass does wrong optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67769 --- Comment #5 from Marek Polacek --- Author: mpolacek Date: Thu Oct 1 19:09:01 2015 New Revision: 228353 URL: https://gcc.gnu.org/viewcvs?rev=228353=gcc=rev Log: PR tree-optimization/67769 * tree-ssa-phiopt.c

[Bug tree-optimization/67769] [6 Regression] VRP pass does wrong optimization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67769 Marek Polacek changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug fortran/67802] ICE on initializing character with wrong len type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67802 --- Comment #1 from Gerhard Steinmetz --- Whereas, without initialization relevant errors are detected : $ cat za1.f90 program p character(1.) :: c1 character(1d1) :: c2 character((0.,1.)) :: c3

[Bug libstdc++/67807] New: call to public member function catalog failed on Linux -std=c++03

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67807 Bug ID: 67807 Summary: call to public member function catalog failed on Linux -std=c++03 Product: gcc Version: 5.1.0 Status: UNCONFIRMED Severity: normal

[Bug c++/54430] [C++11] For-Loop: Scope of iterating variable begins too early

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54430 --- Comment #8 from ville at gcc dot gnu.org --- Author: ville Date: Thu Oct 1 19:22:08 2015 New Revision: 228354 URL: https://gcc.gnu.org/viewcvs?rev=228354=gcc=rev Log: PR c++/54430 /cp 2015-10-01 Ville Voutilainen

[Bug fortran/67804] ICE on data initialization of type(character) with wrong data

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67804 --- Comment #1 from Gerhard Steinmetz --- Correct with a scalar string : $ cat z2.f90 program p type t character :: c end type type(t) :: x data x /t('1')/ print *, x end $ gfortran

[Bug fortran/67805] ICE on array constructor with wrong character specification

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67805 --- Comment #1 from Gerhard Steinmetz --- For these variants : $ cat z4.f90 program p print *, [character([.true.]) :: 'x', 'y'] print *, [character([.false.]) :: 'x', 'y'] print *,

[Bug fortran/67806] New: ICE on initialization of type(character) with len null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67806 Bug ID: 67806 Summary: ICE on initialization of type(character) with len null Product: gcc Version: 5.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug fortran/67804] ICE on data initialization of type(character) with wrong data

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67804 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/67803] ICE on concatenating wrong character array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67803 --- Comment #1 from Gerhard Steinmetz --- Whereas : $ cat z2.f90 program p character(2) :: x(1) x = '0' // [character :: '1'] print *, x end $ gfortran -g -O0 -Wall -fcheck=all

[Bug fortran/67803] New: ICE on concatenating wrong character array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67803 Bug ID: 67803 Summary: ICE on concatenating wrong character array constructor Product: gcc Version: 5.2.1 Status: UNCONFIRMED Severity: normal Priority: P3

[Bug fortran/67802] ICE on initializing character with wrong len type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67802 kargl at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/67779] Strange ordering with strings in extended object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67779 Gerhard Steinmetz changed: What|Removed |Added CC|

[Bug target/51726] LTO and attribute 'selectany'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51726 Kai Tietz changed: What|Removed |Added CC||thiago at kde dot org --- Comment #8 from

[Bug c++/54430] [C++11] For-Loop: Scope of iterating variable begins too early

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54430 Ville Voutilainen changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Bug fortran/67805] New: ICE on array constructor with wrong character specification

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67805 Bug ID: 67805 Summary: ICE on array constructor with wrong character specification Product: gcc Version: 5.2.1 Status: UNCONFIRMED Severity: normal

[Bug fortran/67806] ICE on initialization of type(character) with len null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67806 --- Comment #1 from Gerhard Steinmetz --- Silently accepted without declaring x : $ cat z4b.f90 program p integer, pointer :: n type t character(null(n)) :: c end type end $ gfortran -g

[Bug libstdc++/67791] Crash using std::thread and iostream with dynamic loading of a shared library

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67791 --- Comment #4 from nexyon at gmail dot com --- Thanks for the quick responses! I already expected some sort of side effect like this. Maybe it's possible to reevaluate whether pthread is linked or not during the first use of std::thread? In any

[Bug libstdc++/67747] experimental/filesystem/iterators/recursive_directory_iterator.cc FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67747 Christophe Lyon changed: What|Removed |Added CC||clyon at gcc dot gnu.org --- Comment

[Bug target/67808] LRA ICEs on simple double to long double conversion test case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67808 Peter Bergner changed: What|Removed |Added Target||powerpc64-linux, |

[Bug middle-end/67809] Empty pointer-chasing loops aren't optimized out

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67809 Matt Godbolt changed: What|Removed |Added CC||matt at godbolt dot org --- Comment #1

[Bug target/67808] New: LRA ICEs on simple double to long double conversion test case

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67808 Bug ID: 67808 Summary: LRA ICEs on simple double to long double conversion test case Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/67747] experimental/filesystem/iterators/recursive_directory_iterator.cc FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67747 --- Comment #6 from Jonathan Wakely --- There's a new patch at https://gcc.gnu.org/ml/gcc-patches/2015-10/msg00106.html but I don't know if you're seeing something different.

[Bug fortran/67803] ICE on concatenating wrong character array constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67803 Dominique d'Humieres changed: What|Removed |Added Keywords||ice-on-invalid-code

[Bug middle-end/67809] New: Empty pointer-chasing loops aren't optimized out

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67809 Bug ID: 67809 Summary: Empty pointer-chasing loops aren't optimized out Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: minor Priority: P3 Component:

[Bug c++/67810] New: Non-expression recognized as fold expression

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67810 Bug ID: 67810 Summary: Non-expression recognized as fold expression Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

  1   2   >