[Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783 --- Comment #4 from Paul Smith --- Well, clearly I disagree with this conclusion and feel this is a bug. At the very least, the fact that it's impossible to disable the warning needs to be considered a bug. The statement on the mailing list

[Bug target/85756] [9 regression] wrong code at -Os on x86-64-linux-gnu in 32-bit mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85756 Jakub Jelinek changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug target/85683] [8 Regression] GCC 8 stopped using RMW (Read Modify Write) instructions on x86[_64]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85683 Bug 85683 depends on bug 85756, which changed state. Bug 85756 Summary: [9 regression] wrong code at -Os on x86-64-linux-gnu in 32-bit mode https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85756 What|Removed

[Bug ipa/85787] malloc_candidate_p fails to detect malloc attribute on nested phis

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85787 --- Comment #1 from prathamesh3492 at gcc dot gnu.org --- Working on a patch.

[Bug ipa/85787] New: malloc_candidate_p fails to detect malloc attribute on nested phis

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85787 Bug ID: 85787 Summary: malloc_candidate_p fails to detect malloc attribute on nested phis Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug c/85562] -Wsuggest-attribute=malloc misleads about "returning normally"

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85562 prathamesh3492 at gcc dot gnu.org changed: What|Removed |Added CC||prathamesh3492 at gcc

[Bug ipa/85734] --suggest-attribute=malloc misdiagnoses static functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734 --- Comment #5 from prathamesh3492 at gcc dot gnu.org --- Fixed on trunk.

[Bug fortran/85786] Segfault in associated intrinsic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786 --- Comment #2 from Angus Gibson --- Changing the declaration of e to also be 'target', and associating the pointer: CS%v(2)%p => e if (query_ptr(e, CS)) then ... still causes the segfault. Perhaps I disconnected this from the

[Bug ipa/85734] --suggest-attribute=malloc misdiagnoses static functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734 --- Comment #4 from prathamesh3492 at gcc dot gnu.org --- Author: prathamesh3492 Date: Tue May 15 04:44:33 2018 New Revision: 260249 URL: https://gcc.gnu.org/viewcvs?rev=260249=gcc=rev Log: 2018-05-15 Prathamesh Kulkarni

[Bug fortran/85786] Segfault in associated intrinsic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org ---

[Bug fortran/68950] [fortran] gfc_format_decoder cannot handle %qE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68950 --- Comment #10 from kargl at gcc dot gnu.org --- (In reply to Eric Gallager from comment #9) > (In reply to Tom de Vries from comment #8) > > (In reply to vries from comment #6) > > > posted RFC:

[Bug fortran/85786] New: Segfault in associated intrinsic

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786 Bug ID: 85786 Summary: Segfault in associated intrinsic Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug c++/66662] Request: Change #error directive displaying

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=2 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug fortran/68950] [fortran] gfc_format_decoder cannot handle %qE

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68950 --- Comment #9 from Eric Gallager --- (In reply to Tom de Vries from comment #8) > (In reply to vries from comment #6) > > posted RFC: https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01749.html > > pinged:

[Bug target/65604] MIPS -fno-delayed-branch generates incorrect code with -mcheck-zero-division

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65604 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed|

[Bug tree-optimization/85785] New: missing warning on strcat overflow after strcpy

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85785 Bug ID: 85785 Summary: missing warning on strcat overflow after strcpy Product: gcc Version: 8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783 Martin Sebor changed: What|Removed |Added Keywords||diagnostic

[Bug other/85778] unexpected results with -O2, wrong code?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85778 Scott E. changed: What|Removed |Added CC||sesail999 at gmail dot com --- Comment #2

[Bug libstdc++/84159] filesystem::path::operator/= with has root directory path

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

[Bug tree-optimization/85259] [8/9 Regression] Missing -Wstringop-overflow= since r256683

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85259 Martin Sebor changed: What|Removed |Added Keywords||patch --- Comment #5 from Martin Sebor

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 --- Comment #4 from Jonathan Wakely --- Author: redi Date: Mon May 14 22:35:44 2018 New Revision: 260244 URL: https://gcc.gnu.org/viewcvs?rev=260244=gcc=rev Log: PR libstdc++/67554 Do not pass null pointers to memcpy PR libstdc++/67554

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

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

[Bug libstdc++/82966] node_handle swap fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82966 Jonathan Wakely changed: What|Removed |Added Keywords||rejects-valid

[Bug libstdc++/82966] node_handle swap fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82966 --- Comment #3 from Jonathan Wakely --- Author: redi Date: Mon May 14 22:22:23 2018 New Revision: 260242 URL: https://gcc.gnu.org/viewcvs?rev=260242=gcc=rev Log: PR libstdc++/82966 fix swapping of node handles PR libstdc++/82966

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 --- Comment #3 from Jonathan Wakely --- Author: redi Date: Mon May 14 22:22:27 2018 New Revision: 260243 URL: https://gcc.gnu.org/viewcvs?rev=260243=gcc=rev Log: PR libstdc++/67554 Do not pass null pointers to memcpy PR libstdc++/67554

[Bug libstdc++/81256] basic_filebuf::close doesn't propagate exceptions

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

[Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698 --- Comment #7 from Pat Haugen --- So the problem is that we're generating a stxvw4x insn to write to memory, which corrupts the contents due to both endian behavior and element size (since we're dealing with halfword/uint16_t elements). Value

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Mon May 14 21:51:51 2018 New Revision: 260241 URL: https://gcc.gnu.org/viewcvs?rev=260241=gcc=rev Log: PR libstdc++/67554 Do not pass null pointers to memcpy PR libstdc++/67554

[Bug libstdc++/82966] node_handle swap fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82966 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Mon May 14 21:51:46 2018 New Revision: 260240 URL: https://gcc.gnu.org/viewcvs?rev=260240=gcc=rev Log: PR libstdc++/82966 fix swapping of node handles PR libstdc++/82966

[Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783 --- Comment #2 from Paul Smith --- > Did you try: -Wno-alloc-size-larger-than ? Yes. cc1plus: error: unrecognized command line option '-Wno-alloc-size-larger-than' > Also in your code, numberFields is a signed int and then casted to size_t.

[Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783 --- Comment #1 from Andrew Pinski --- Did you try: -Wno-alloc-size-larger-than ? Also in your code, numberFields is a signed int and then casted to size_t. On LP64 targets (or rather sizeof(size_t) != sizeof(int)), then value is sign extended.

[Bug fortran/85781] ICE in gfc_build_array_ref, at fortran/trans.c:393

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85781 Dominique d'Humieres changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/85784] New: False positive with -Wunused-but-set-parameter

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85784 Bug ID: 85784 Summary: False positive with -Wunused-but-set-parameter Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug c++/85783] New: alloc-size-larger-than fires incorrectly with new[] and can't be disabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783 Bug ID: 85783 Summary: alloc-size-larger-than fires incorrectly with new[] and can't be disabled Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity:

[Bug middle-end/85602] -Wsizeof-pointer-memaccess for strncat with size of source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85602 --- Comment #4 from Paul Eggert --- Thanks, that workaround is much better for coreutils, and I installed it here: https://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=f6cb50cc991d461f443ea3afc517c9e1e37ef496

[Bug fortran/85780] ICE in resolve_fl_procedure, at fortran/resolve.c:12504

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85780 --- Comment #2 from kargl at gcc dot gnu.org --- (In reply to kargl from comment #1) > HOwever, I think we then have an accepts invalid as an alternate > return takes a label. Whoops, I may have misread the standard. The label applies to the

[Bug fortran/85780] ICE in resolve_fl_procedure, at fortran/resolve.c:12504

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

[Bug target/85756] [9 regression] wrong code at -Os on x86-64-linux-gnu in 32-bit mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85756 --- Comment #4 from Eric Botcazou --- Author: ebotcazou Date: Mon May 14 20:17:19 2018 New Revision: 260239 URL: https://gcc.gnu.org/viewcvs?rev=260239=gcc=rev Log: PR target/85756 * gnat.dg/opt70.adb: New test. *

[Bug middle-end/85602] -Wsizeof-pointer-memaccess for strncat with size of source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85602 --- Comment #3 from Martin Sebor --- I agree that's not an improvement. Would something like this be better? (at least until utmp_ent is marked nonstring and GCC taught to suppress the diagnostic) size_t utmpsize = sizeof UT_ID (utmp_ent);

[Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698 --- Comment #6 from Pat Haugen --- (In reply to Richard Biener from comment #4) > I can see what the patch does to this testcase on x86_64 - it enables BB > vectorization of the first two loops after runrolling. I don't see anything >

[Bug fortran/85779] ICE in gfc_typename, at fortran/misc.c:156

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

[Bug c++/85782] New: acc loops with continue statements ICE in c++

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85782 Bug ID: 85782 Summary: acc loops with continue statements ICE in c++ Product: gcc Version: 8.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug middle-end/85602] -Wsizeof-pointer-memaccess for strncat with size of source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85602 --- Comment #2 from Paul Eggert --- Thanks for looking into it. For what it's worth, the practical effect of this new warning was that I changed that part of coreutils to not use strncat, causing 3 lines of code to grow to 8 lines. See the end

[Bug fortran/85781] ICE in gfc_build_array_ref, at fortran/trans.c:393

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85781 --- Comment #1 from G. Steinmetz --- Some variants that are actually compiling : $ cat z2.f90 subroutine s(x) bind(c) use iso_c_binding, only: c_char character(kind=c_char), value :: x print *, x(1:0) end $ cat

[Bug fortran/85781] New: ICE in gfc_build_array_ref, at fortran/trans.c:393

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85781 Bug ID: 85781 Summary: ICE in gfc_build_array_ref, at fortran/trans.c:393 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug fortran/85780] New: ICE in resolve_fl_procedure, at fortran/resolve.c:12504

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85780 Bug ID: 85780 Summary: ICE in resolve_fl_procedure, at fortran/resolve.c:12504 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal

[Bug fortran/85779] ICE in gfc_typename, at fortran/misc.c:156

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85779 --- Comment #1 from G. Steinmetz --- Related : $ cat z3.f90 class(t) function f() type f end type end $ gfortran-9-20180513 -c z3.f90 f951: internal compiler error: Segmentation fault 0xb9f4bf crash_signal

[Bug fortran/85779] New: ICE in gfc_typename, at fortran/misc.c:156

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85779 Bug ID: 85779 Summary: ICE in gfc_typename, at fortran/misc.c:156 Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran

[Bug libstdc++/81256] basic_filebuf::close doesn't propagate exceptions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81256 --- Comment #2 from Jonathan Wakely --- Author: redi Date: Mon May 14 18:57:45 2018 New Revision: 260236 URL: https://gcc.gnu.org/viewcvs?rev=260236=gcc=rev Log: PR libstdc++/81256 fix exception handling in basic_filebuf::close PR

[Bug other/85778] unexpected results with -O2, wrong code?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85778 --- Comment #1 from Andrew Pinski --- It depends on if glibc is adding the nonnull attribute to stat or is it GCC. Also what does the C (and POSIX) standard says about a null pointer being passed as the string to stat.

[Bug middle-end/85602] -Wsizeof-pointer-memaccess for strncat with size of source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85602 Martin Sebor changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug other/85778] New: unexpected results with -O2, wrong code?

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85778 Bug ID: 85778 Summary: unexpected results with -O2, wrong code? Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other

[Bug libstdc++/85768] [9 Regression] FreeBSD bootstrap fails due to undefined reference to 'backtrace'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85768 François Dumont changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |fdumont at gcc dot gnu.org

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #12 from Jan --- And yes I use a gentoo system. But I'm using the gcc patches from clear linux but this bug doesn't seem relate to that.

[Bug lto/85759] ICE output_profile_summary, at lto-cgraph.c:706 using -profile-use

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85759 --- Comment #11 from Jan --- I can reproduce it with vanilla gcc 8.1.0 no patches applied.

[Bug c++/85739] [8/9 Regression] internal compiler error: in finish_member_declaration, at cp/semantics.c:3057

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85739 ensadc at mailnesia dot com changed: What|Removed |Added CC||ensadc at mailnesia dot com

[Bug target/85769] [8/9 Regression] ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85769 Tamar Christina changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug libstdc++/71098] uniform initialization for nested tuples work in c++11/14 mode but should only work >=c++17

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

[Bug target/85756] [9 regression] wrong code at -Os on x86-64-linux-gnu in 32-bit mode

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85756 --- Comment #3 from uros at gcc dot gnu.org --- Author: uros Date: Mon May 14 15:53:58 2018 New Revision: 260231 URL: https://gcc.gnu.org/viewcvs?rev=260231=gcc=rev Log: PR target/85756 * config/i386/i386.md: Disallow

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Mon May 14 15:35:06 2018 New Revision: 260229 URL: https://gcc.gnu.org/viewcvs?rev=260229=gcc=rev Log: PR libstdc++/67554 Do not pass null pointers to memcpy PR libstdc++/67554

[Bug ipa/85656] gcc.dg/ipa/ipa-icf-38.c FAILs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 --- Comment #5 from ro at CeBiTec dot Uni-Bielefeld.DE --- > --- Comment #4 from Martin Liška --- [...] > According to log file alias support is mission on solaris. Thus following > patch > should fix that by skipping the test: > > diff --git

[Bug sanitizer/85777] [7/8 Regression] -fsanitize=undefined makes a -Wmaybe-uninitialized warning disappear

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777 --- Comment #1 from Vincent Lefèvre --- I've cleaned up the testcase: int d; int h(void); void e(void) { int f[2]; int g = 0; if (d) g++; if (d == 1) f[g++] = 2; (void) (f[0] || (g && h())); } Now: cventin% gcc-snapshot

[Bug sanitizer/85777] New: [7/8 Regression] -fsanitize=undefined makes a -Wmaybe-uninitialized warning disappear

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85777 Bug ID: 85777 Summary: [7/8 Regression] -fsanitize=undefined makes a -Wmaybe-uninitialized warning disappear Product: gcc Version: 9.0 Status: UNCONFIRMED

[Bug libstdc++/82966] node_handle swap fails to compile

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82966 --- Comment #1 from Jonathan Wakely --- Author: redi Date: Mon May 14 14:27:54 2018 New Revision: 260226 URL: https://gcc.gnu.org/viewcvs?rev=260226=gcc=rev Log: PR libstdc++/82966 fix swapping of node handles PR libstdc++/82966

[Bug c++/85776] New: ICE when compiling `boost::thread` with `-std=c++11` on mingw-w64

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85776 Bug ID: 85776 Summary: ICE when compiling `boost::thread` with `-std=c++11` on mingw-w64 Product: gcc Version: 8.1.1 Status: UNCONFIRMED Severity: normal

[Bug c++/85775] New: False positive with -Wparentheses

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85775 Bug ID: 85775 Summary: False positive with -Wparentheses Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/85731] [8/9 Regression] Inner class method declaration changes meaning of outer template class template method

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

[Bug sanitizer/85774] New: Incorrect stack-use-after-scope caused by missing cleanup of shadow bytes

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85774 Bug ID: 85774 Summary: Incorrect stack-use-after-scope caused by missing cleanup of shadow bytes Product: gcc Version: 8.1.1 Status: UNCONFIRMED Severity:

[Bug libstdc++/85184] Remove __glibcxx_assert uses from std::variant

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

[Bug libstdc++/85319] std::char_traits::length does not always function in constexpr context

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

[Bug libstdc++/82966] node_handle swap fails to compile

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

[Bug libstdc++/82452] defines macros for getc and putc

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

[Bug libstdc++/81522] c++17/old-abi/cygwin empty stringstream invalid memory access

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81522 --- Comment #1 from Jonathan Wakely --- Possibly related to PR 82172 (which was due to a binutils bug) but that apparently only occurs when using LTO.

[Bug libstdc++/81263] Work around CWG issue 1558 (guarantee SFINAE when using `void_t`)

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

[Bug libstdc++/81256] basic_filebuf::close doesn't propagate exceptions

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

[Bug libstdc++/72830] istream::seekg should not reset eofbit if -std=c++98

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

[Bug libstdc++/71301] std::tuple move constructor

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

[Bug libstdc++/71098] uniform initialization for nested tuples work in c++11/14 mode but should only work >=c++17

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

[Bug libstdc++/69191] Wrong equality comparison between error_code and error_condition + segfault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69191 --- Comment #17 from Jonathan Wakely --- (In reply to Chip Salzenberg from comment #16) > Still happening in 7.2 What is?

[Bug libstdc++/67011] division by zero in std::exponential_distribution

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

[Bug libstdc++/67554] runtime error in valarray (NULL passed to memcpy)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67554 Jonathan Wakely changed: What|Removed |Added Keywords||wrong-code

[Bug libstdc++/62119] dangling reference : gslice_array's copy constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62119 --- Comment #4 from Jonathan Wakely --- PR 63314 points out the same problem exists in mask_array and indirect_array.

[Bug libstdc++/63314] valarray mask/indices refers to temporary

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

[Bug libstdc++/62119] dangling reference : gslice_array's copy constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62119 Jonathan Wakely changed: What|Removed |Added CC||helloworld922 at hotmail dot com ---

[Bug libstdc++/62196] running time segment fault with valarray

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

[Bug libstdc++/85773] Embedded nulls in filesystem::path cause problems

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

[Bug libstdc++/85773] New: Embedded nulls in filesystem::path cause problems

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85773 Bug ID: 85773 Summary: Embedded nulls in filesystem::path cause problems Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug libstdc++/85772] __gnu_cxx::__versa_string doesn't support C++11 allocators

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

[Bug libstdc++/85772] __gnu_cxx::__versa_string doesn't support C++11 allocators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85772 --- Comment #1 from Jonathan Wakely --- Also review it for noexcept, so that for example the copy constructor is noexcept when using the COW base: diff --git a/libstdc++-v3/include/ext/rc_string_base.h

[Bug libstdc++/85771] `std::variant<...>` insanely slow to compile compared to `union` (256 types)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85771 --- Comment #1 from Jonathan Wakely --- This should be completely unsurprising, obviously std::variant is different to a union. The type safety and other features come at a cost, and 2s isn't insane.

[Bug libstdc++/85772] New: __gnu_cxx::__versa_string doesn't support C++11 allocators

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85772 Bug ID: 85772 Summary: __gnu_cxx::__versa_string doesn't support C++11 allocators Product: gcc Version: 9.0 Status: UNCONFIRMED Severity: enhancement

[Bug libstdc++/62119] dangling reference : gslice_array's copy constructor

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

[Bug libstdc++/85771] New: `std::variant<...>` insanely slow to compile compared to `union` (256 types)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85771 Bug ID: 85771 Summary: `std::variant<...>` insanely slow to compile compared to `union` (256 types) Product: gcc Version: 8.1.0 Status: UNCONFIRMED Severity:

[Bug libstdc++/84118] filesystem::path concat does not accept value_type

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

[Bug target/85770] New: [9 Regression] ICE: in lra_eliminate, at lra-eliminations.c:1439 with -march=nano-1000

x86_64-pc-linux-gnu-as --disable-libstdcxx-pch --prefix=/repo/gcc-trunk//binary-trunk-260223-checking-yes-rtl-df-extra-nobootstrap-amd64 Thread model: posix gcc version 9.0.0 20180514 (experimental) (GCC)

[Bug target/85769] [8/9 Regression] ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85769 --- Comment #2 from Tamar Christina --- It's not r250673, That was committed 2017-07-28 and a GCC built 2017-08-17 does the correct thing for non-Armv8.2-a. It promotes the fp16 values to 32 bits does the operations and converts them back to

[Bug libstdc++/83891] std::filesystem::path::is_absolute for Windows

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

[Bug libstdc++/85768] [9 Regression] FreeBSD bootstrap fails due to undefined reference to 'backtrace'

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85768 --- Comment #2 from Jonathan Wakely --- Yes I did suggest that. For now I think we should just disable the use of backtrace anywhere except GNU/Linux.

[Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 --- Comment #23 from rguenther at suse dot de --- On Mon, 14 May 2018, glisse at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 > > --- Comment #22 from Marc Glisse --- > (In reply to rguent...@suse.de from

[Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899 --- Comment #22 from Marc Glisse --- (In reply to rguent...@suse.de from comment #21) > Note that in the strict C semantic thing __restrict on > this isn't valid as the following is valid C++: > > Foo() __restrict > { > Foo *x = this; >

  1   2   >