[Bug libstdc++/100903] Bogus "zero as null pointer constant" warning

2023-11-20 Thread headch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100903 --- Comment #13 from Christopher Head --- Could the error message be made more readable by trying to call an undefined-but-declared non-consteval function inside the consteval context in the error case, rather than throwing? The name of the func

[Bug c++/110861] Bad codegen leading to runtime segfault when mixing import and #include

2023-07-31 Thread headch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110861 --- Comment #1 from Christopher Head --- Note that I ran into this while trying to find a small repro case for the same symptoms (uninitialized “this” and segfault using a string_view) in a larger project, where I originally saw the same thing h

[Bug c++/110861] New: Bad codegen leading to runtime segfault when mixing import and #include

2023-07-31 Thread headch at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- $ g++-13 --version g++-13 (Gentoo 13.2.0 p3) 13.2.0 Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see

[Bug c++/109001] New: “no declaration matches” for complicated non-type template parameters

2023-03-02 Thread headch at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- I’m reasonably certain (but not completely) that this is valid code: #include #include template class C { public: template C set

[Bug c++/101901] "warning: statement has no effect" in a variadic template with empty parameter pack.

2022-01-07 Thread headch at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101901 Christopher Head changed: What|Removed |Added CC||headch at gmail dot com --- Comment

[Bug c++/99778] New: Spurious -Wzero-as-null-pointer-constant on three-way comparisons

2021-03-25 Thread headch at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- Consider the following code: #include #include int main() { std::strong_ordering o = 1 <=> 2; if(

[Bug c++/99272] New: False positive -Wredundant-tags warning when reusing a name

2021-02-25 Thread headch at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- $ cat test.cpp struct foo { int x; }; struct bar { struct foo foo; }; $ g++-10.2.0 -Wall -Wextra -Wredundant-tags -std=c++2a

[Bug c++/98947] New: Incorrect warning when using a ternary operator to select one of two volatile variables to write to

2021-02-02 Thread headch at gmail dot com via Gcc-bugs
: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- Using a ternary operator to select one of two variables of the same volatile-qualified type and then

[Bug c++/80078] Incorrect classification of address of volatile as not constant

2019-08-21 Thread headch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80078 Christopher Head changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/80078] Incorrect classification of address of volatile as not constant

2019-08-08 Thread headch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80078 --- Comment #3 from Christopher Head --- I tried 9.1 at gcc.godbolt.org and it looks like this is fixed. Anyone else care to take a look? If there are no further comments, I guess I’ll close this ticket in a few days.

[Bug inline-asm/63900] memory constrains needlessly doing memory clobber

2018-10-23 Thread headch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63900 --- Comment #9 from Christopher Head --- I had to use slightly different code because I only have an ARM cross-compiler version 8.2.0 installed, so I used this: void g(unsigned char x); struct MyStruct { char foo[8]; }; unsigned char b

[Bug inline-asm/63900] memory constrains needlessly doing memory clobber

2018-09-29 Thread headch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63900 Christopher Head changed: What|Removed |Added CC||headch at gmail dot com --- Comment

[Bug c++/80078] Incorrect classification of address of volatile as not constant

2018-09-23 Thread headch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80078 Christopher Head changed: What|Removed |Added Known to fail||8.2.0 --- Comment #2 from Christopher

[Bug c++/82294] New: Array of objects with constexpr constructors initialized from space-inefficient memory image

2017-09-22 Thread headch at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- Consider the following code: $ cat test.cpp struct S { int x; explicit constexpr S

[Bug target/82038] Very poor optimization of constant multiply on ARM Cortex-M7

2017-08-30 Thread headch at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82038 --- Comment #2 from Christopher Head --- I think they do. Just one example, but I’m pretty sure it holds for others too (left-shift equals multiply by power of two, even for negative integers; it’s right-shift where the behaviour differs due to d

[Bug target/82038] New: Very poor optimization of constant multiply on ARM Cortex-M7

2017-08-30 Thread headch at gmail dot com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- Consider the following source code: #include int64_t f(int32_t x) { return x * 16384LL; } int64_t g(int32_t x) { return

[Bug c++/80078] New: Incorrect classification of address of volatile as not constant

2017-03-16 Thread headch at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- Consider the following code: volatile int ary[1]; static_assert(&ary[0], ""); static_assert(ary + 0, ""); The f

[Bug target/79237] New: ARMv7-M ICE in extract_constrain_insn, insn does not satisfy its constraints

2017-01-26 Thread headch at gmail dot com
: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: headch at gmail dot com Target Milestone: --- Created attachment 40585 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40585&action=edit Source code reproduc

[Bug c++/48446] New: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:1946

2011-04-04 Thread headch at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48446 Summary: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.c:1946 Product: gcc Version: 4.4.5 Status: UNCONFIRMED Severity: normal Priority: P3