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
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
: 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
: 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101901
Christopher Head changed:
What|Removed |Added
CC||headch at gmail dot com
--- Comment
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(
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
: 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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80078
Christopher Head changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
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.
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
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63900
Christopher Head changed:
What|Removed |Added
CC||headch at gmail dot com
--- Comment
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
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
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
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
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
: 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
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
19 matches
Mail list logo