http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52347
Simon Richter Simon.Richter at hogyros dot de changed:
What|Removed |Added
CC
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52347
--- Comment #4 from Simon Richter Simon.Richter at hogyros dot de ---
Testcase is simple:
$ cat tt.cpp
void bar(int baz) { }
$ g++-4.7 -c -W -Wall -Werror -Wno-unused tt.cpp
$ g++-4.8 -c -W -Wall -Werror -Wno-unused tt.cpp
tt.cpp:1:6: error
Severity: minor
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
This is a bit of a corner/academic case, but came up in a Stack Overflow
discussion:
struct Base
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
Created attachment 41742
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41742=edit
Generated assembler code
Compiling the code
#incl
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
The code
char const array1[2] = { 'a', 'b' };
char const array2[2] = { 'c', 'd' };
char foo(bool b) {
char const ()[2] = b ? array1 : array2
: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
With the code
struct A { virtual void foo() = 0; };
struct B : A { virtual void foo() {} void bar() const; };
void test(A *a)
{
if(auto b = dynamic_cast
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87634
--- Comment #2 from Simon Richter ---
Well, I tried really hard to make a case that makes the second dynamic_cast
return null after the first returned non-null.
The most promising candidate uses a direct destructor call and placement new on
a
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
Similar to #78291:
struct foo
{
foo operator+(foo const ) const { throw
: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
Similar to #88176:
struct one {};
struct two
{
two() { }
two(one const &) { }
operator one() const { return one{}; }
++
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
Similar to #89563, but even more minimal:
#include
struct one {};
struct two
{
two() { }
two(one const &) { }
operator one() const { return
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
I'm currently refactoring a program that uses a preprocessor symbol in various
places, and I'd like to generate errors for all uses.
There is no common
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
While [building GHDL 3.0.0]() on Debian, using gcc 12 as a base, we get an ICE:
aarch64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109930
--- Comment #5 from Simon Richter ---
> Btw if you know the old state then there is presumably no concurrent access
> here and so you don't need atomic, let alone sequential consistency.
I know it in some, but not all cases.
Basically, what
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109930
--- Comment #3 from Simon Richter ---
I was looking at ARMv7 initially.
If I understood the implementation correctly, this can be a generic
optimization.
: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
I'm not sure if that is a valid substitution, but...
I have a state machine that has a few transitions
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
On RISC-V with -O3,
#include
extern uint32_t volatile d;
extern uint8_t volatile o;
void f()
{
uint32_t t;
while((t = d) & 0x8000)
;
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
On RISC-V with -O3, the C++ program
int f() {}
emits a completely empty function.
It correctly warns about the missing
ty: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Simon.Richter at hogyros dot de
Target Milestone: ---
We have an object that contains several sub-objects that should reference each
other through interface pointers. I'd like to
18 matches
Mail list logo
