https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85505
--- Comment #3 from James Abbatiello ---
I ran into this again. I can confirm that it still affects the latest trunk.
https://gcc.godbolt.org/z/W79a1vvWa succeeds when it should be rejected.
Is there any chance that somebody could take another
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
When building the following example, a linker error is produced.
```
void foo();
template class DynArray
: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
When building the following example, a `-Wodr` warning is shown. I don't think
the code violates the ODR so this wa
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
Created attachment 56086
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56086&action=edit
Reproducer
The
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
Compiling:
double test(int *arr, int x) {
double ret(double(arr[x]) + 1);
return ret;
}
produces:
: In function
: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
There is a problem when having two different variables both of which are const
references
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
The following code is accepted by GCC although I believe it should not be.
This happens on all versions and all platforms currently
NCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
This occurs with any version of GCC that I've tried that recognizes -std=c++11.
It seems to affe
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
Created attachment 41130
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41130&action=edit
Testcas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77306
--- Comment #1 from James Abbatiello ---
Created attachment 39478
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39478&action=edit
Patch
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
Created attachment 39477
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39477&action=edit
Reproducer
This bug is being fil
++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
Created attachment 39473
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39473&action=edit
Test case
Testcase:
struct Rec {
unsigned char data[1]; // actually variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71154
--- Comment #3 from James Abbatiello ---
Andrew Pinsky, I'm not sure I understand your comment. Why would the
visibility of D be affected by the visibility of C? If I change your test
case so that C is declared as hidden before the definition o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71154
--- Comment #1 from James Abbatiello ---
Created attachment 38502
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38502&action=edit
Too simple patch
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: abbeyj+gcc at gmail dot com
Target Milestone: ---
Created attachment 38501
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38501&action=edit
Reproducer
Trying to apply attribute
15 matches
Mail list logo
