https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112288
--- Comment #9 from Fabio Alemagna ---
(In reply to Patrick Palka from comment #8)
> The issue was probably latent before r6-6830. The testcase is kind of
> strange,
It's the "friend injection" technique. In this case, it's used to create a
co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112288
--- Comment #7 from Fabio Alemagna ---
(In reply to Marek Polacek from comment #6)
> (In reply to Andrew Pinski from comment #5)
> > (In reply to Fabio Alemagna from comment #4)
> > > (In reply to Marek Polacek from comment #2)
> > > > Confirmed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112288
--- Comment #4 from Fabio Alemagna ---
(In reply to Marek Polacek from comment #2)
> Confirmed. Started with r6-6830-g20a0c6f9bdbd78:
>
> commit 20a0c6f9bdbd781ed5d413a10a06764a174dc394
> Author: Patrick Palka
> Date: Mon Feb 8 23:02:50 201
||
CC||falemagn at gmail dot com
--- Comment #1 from Fabio Alemagna ---
Created attachment 56474
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56474&action=edit
Generated with -freport-bug
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
It's a regression, it compiles fine with v13.2.1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #4 from Fabio Alemagna ---
With a tweak(In reply to Andrew Pinski from comment #3)
> (In reply to Fabio Alemagna from comment #1)
> > Changing the return type of the function func() from int to auto makes the
> > warning disappear.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #2 from Fabio Alemagna ---
Sorry, "from int to auto" should have been "from bool to auto". You get the
point.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112267
--- Comment #1 from Fabio Alemagna ---
Changing the return type of the function func() from int to auto makes the
warning disappear.
Incidentally it causes an error on clang, though, which prompts the question:
is this a clang bug, for erroring
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
I am expecting no warnings from the following code snippets, especially because
SFINAE is being correctly trig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109728
--- Comment #2 from Fabio Alemagna ---
Yes, clang handles this case correctly.
y: P3
Component: objc++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
This simple snippet
int a;
auto b = [c = a]{};
Produces the following error:
error: 'c' was not declared in this scope
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108089
Fabio Alemagna changed:
What|Removed |Added
Known to work||11.3.0
Known to fail|
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
The following is the most reduced example I could come up with.
#include
#include
#include
using variant = std
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
Created attachment 54083
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54083&action=edit
Preprocessed file
The following
: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
This code fails to compile with g++12.
struct test
{
template
int
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89565
--- Comment #4 from Fabio Alemagna ---
Just encountered this bug myself, with trunk gcc (11.0.1 20210321
(experimental)).
See godbolt: https://godbolt.org/z/TxW137Whh
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70462
--- Comment #7 from Fabio Alemagna ---
(In reply to Pádraig Brady from comment #6)
> This does introduce an ABI incompatibility.
>
> I'm seeing this with kuduraft-1.8 compiled with GCC 10, giving linker errors
> from clang 9.0.20190721 like:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513
Fabio Alemagna changed:
What|Removed |Added
CC||falemagn at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85153
--- Comment #4 from Fabio Alemagna ---
@(In reply to Richard Biener from comment #3)
> Confirmed. Not sure what the exact limit is but some of the warnings can
> only be disabled at function granularity and placing the pragmas in macros
> might
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85153
--- Comment #2 from Fabio Alemagna ---
And removing the exclamation mark from the if condition actually makes it work
again, but only if the B and E macro are wrapped within the Y() macro,
otherwise it still complains, now indicating the parenthe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85153
Fabio Alemagna changed:
What|Removed |Added
Attachment #43809|0 |1
is obsolete|
: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
Created attachment 43809
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=43809&
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79362
--- Comment #2 from Fabio Alemagna ---
I had looked for possible duplicates but found none, sorry about that and glad
to know it's already been fixed. Thanks for your time!
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: falemagn at gmail dot com
Target Milestone: ---
I cannot reproduce the bug locally, so I cannot provide more details, but it
does happen on godbolt where I was experimenting with
24 matches
Mail list logo
