[Bug c++/94751] New: [9/10] ICE on invalid code in maybe_instantiate_noexcept

2020-04-24 Thread s...@li-snyder.org
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - gcc version: gcc version 10.0.1 20200329 (experimental) (GCC) ICEs on the following (invalid) input: -- x.cc

[Bug c++/93138] New: [10 regression] elaborated type specifier visibility check problem

2020-01-02 Thread s...@li-snyder.org
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - With this version of gcc10 (svn rev 279832): gcc version 10.0.0 20200102 (experimental) (GCC) This source does not compile: -- x.cc

[Bug c++/93137] New: [10 regression] ICE in refs_may_alias_p_2

2020-01-02 Thread s...@li-snyder.org
++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - With this version of gcc10 (svn rev 279832): gcc version 10.0.0 20200102 (experimental) (GCC) this source gives an ICE when compiled with -O: -- x.cc

[Bug c++/88485] New: [9 regression] parse error on explicitly specialized assignment call

2018-12-13 Thread s...@li-snyder.org
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - gcc9 rejects the following code: - template class Base {}; class Block

[Bug c++/88385] New: [9 regression] ICE in tsubst_pack_expansion

2018-12-05 Thread s...@li-snyder.org
++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - gcc 20181205 gets an ICE compiling this code. (8.2.1 compiles it without error.) thanks, sss -- template struct xtest

[Bug c++/86374] New: [8 regression] template member name lookup problem

2018-07-02 Thread s...@li-snyder.org
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - With gcc checked out on 2018-07-01 from gcc-8-branch (rev 262277, tested on x86_64-pc-linux-gnu [fedora 28]), this input: -- y.cc

[Bug middle-end/61037] array-bounds false positive

2018-01-17 Thread s...@li-snyder.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61037 scott snyder <s...@li-snyder.org> changed: What|Removed |Added Status|UNCONFIRMED |RE

[Bug c++/83919] New: [8 regression] spurious -Wignored-qualifiers warning

2018-01-17 Thread s...@li-snyder.org
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- With gcc version gcc version 8.0.1 20180115 (experimental) (GCC) compiling this source with -Wextra -std=c++17 gets a warning: -- x.cc

[Bug c++/83690] New: [8 regression] spurious unused variable warings for variables used only in static_assert

2018-01-04 Thread s...@li-snyder.org
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- As of gcc version 8.0.0 20180102 (experimental) (GCC) gcc gives an unused-but-set warning for variables that are used

[Bug c++/79091] [7 regression] ICE in write_unnamed_type

2017-01-19 Thread s...@li-snyder.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79091 --- Comment #7 from scott snyder <s...@li-snyder.org> --- Confirmed that this fixes the original problem from which the test case was derived. Thanks!

[Bug c++/79159] New: [7 regression] spurious array-bounds warning

2017-01-19 Thread s...@li-snyder.org
++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - gcc version 7.0.0 20170119 gives what appears to be a spurious warning for this example when compiling with -O3 (tested on x86_64-pc-linux-gnu

[Bug c++/79095] New: [7 regression] spurious stringop-overflow warning

2017-01-15 Thread s...@li-snyder.org
: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - gcc version 7.0.0 20170111 gives what appears to be a spurious warning for this example when compiling with -O3 (tested on x86_64-pc-linux-gnu

[Bug c++/79091] New: [7 regression] ICE in write_unnamed_type

2017-01-14 Thread s...@li-snyder.org
++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- hi - gcc version 7.0.0 20170111 gives an ICE for this example (tested on x86_64-pc-linux-gnu): enum { ColMajor = 0

[Bug c++/79077] New: [7 regression][new inheriting ctors] bad code for inherited ctor

2017-01-12 Thread s...@li-snyder.org
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- Target: x86_64-pc-linux-gnu hi - This bug may be related to 78495. gcc version 7.0.0 20170111 generates bad code for this example

[Bug middle-end/67821] New: [gcc 5 regression] ICE in duplicate_ssa_name_range_info

2015-10-02 Thread s...@li-snyder.org
Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org Target Milestone: --- Created attachment 36438 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=36438=edit test case hi - I'm testing gcc from the gcc-5-branch

[Bug middle-end/61037] New: array-bounds false positive

2014-05-02 Thread s...@li-snyder.org
Assignee: unassigned at gcc dot gnu.org Reporter: s...@li-snyder.org hi - I'm using gcc from the 4.9 branch: GNU C++ (GCC) version 4.9.1 20140502 (prerelease) (x86_64-unknown-linux-gnu) compiled by GNU C version 4.9.1 20140502 (prerelease), GMP version 5.1.2, MPFR version 3.1.2, MPC