[Bug c++/93259] Unsized temporary array initialization problem

2023-12-12 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93259 --- Comment #7 from m.cencora at gmail dot com --- This seems to be fixed in gcc 12.3 and gcc 13+ Can we close this?

[Bug c++/113064] New: assignement from temporary sometimes invokes copy-assign instead of move-assign operator

2023-12-18 Thread m.cencora at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- Following code fails to compile on any gcc version with any selected language version. Works with clang. When

[Bug c++/113064] assignement from temporary sometimes invokes copy-assign instead of move-assign operator

2023-12-18 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113064 --- Comment #1 from m.cencora at gmail dot com --- Fixed sample (a typo in else branch of WORKAROUND2): struct no_copy { no_copy() = default; no_copy(const no_copy&) = delete; no_copy(no_copy&&); no_copy&

[Bug c++/113064] assignement from temporary sometimes invokes copy-assign instead of move-assign operator

2023-12-18 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113064 --- Comment #2 from m.cencora at gmail dot com --- > When invoking the conversion operator the problem does not occur. When invoking the conversion operator *explicitly* the problem does not occur.

[Bug c++/113064] assignement from temporary sometimes invokes copy-assign instead of move-assign operator

2023-12-19 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113064 --- Comment #4 from m.cencora at gmail dot com --- This also might be a just another symptom of the same root cause: struct bar { bar() = default; bar(const bar&); bar(bar&&); bar& operator=(const bar&);

[Bug c++/113064] assignement from temporary sometimes invokes copy-assign instead of move-assign operator

2023-12-19 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113064 --- Comment #5 from m.cencora at gmail dot com --- (In reply to m.cencora from comment #4) > This also might be a just another symptom of the same root cause: This one is actually a regression (worked on gcc 8.3 and older)

[Bug c++/113219] New: Overloaded ref-qualified conversion operator triggers bogus -Wconversion

2024-01-03 Thread m.cencora at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- Following code when compiled on any gcc version (checked all available on godbolt since gcc-7) triggers conversion warnings. I

[Bug c++/113219] Overloaded ref-qualified conversion operator triggers bogus -Wconversion

2024-01-04 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113219 --- Comment #2 from m.cencora at gmail dot com --- So I guess this falls into the "confusing overload resolution for user-defined conversion" but I fail to see what can be confusing here. createInt() returns prvalue, so later it binds

[Bug c++/113064] assignement from temporary sometimes invokes copy-assign instead of move-assign operator

2024-01-04 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113064 --- Comment #11 from m.cencora at gmail dot com --- This is surprising to say the least because apparently for following code (where both conversion operators return same type) the compiler somehow correctly chooses && qualified

[Bug c++/115445] New: [15 Regression] ICE when repeating an export of function declared in GMF

2024-06-11 Thread m.cencora at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- $ cat repeated_using.cpp module; namespace std { void make_error_code(); } export module std; export namespace std

[Bug c++/115446] New: [15 Regression] Segfault when exporting operator new

2024-06-11 Thread m.cencora at gmail dot com via Gcc-bugs
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- $ cat op_new.cpp module; void* operator new(unsigned long, void*); namespace std { template auto construct_at(_Tp*) -> decltype(::new((void*)0) _Tp()) { ret

[Bug c++/115445] [15 Regression] [modules] ICE when repeating an export of function declared in GMF

2024-06-11 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115445 --- Comment #1 from m.cencora at gmail dot com --- Works fine on gcc-14 and clang

[Bug libstdc++/106852] Implement C++23 P2465R3 Standard Library Modules std and std.compat

2024-06-12 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106852 m.cencora at gmail dot com changed: What|Removed |Added CC||m.cencora at gmail dot com

[Bug c++/114600] [14 Regression] [modules] redefinition errors when using certain std headers in GMF

2024-06-13 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114600 --- Comment #15 from m.cencora at gmail dot com --- Thanks! Unfortunately it seems that your changes broke reexporting of types declared in other module. It works fine on gcc-14. $ cat base.cpp module; #include export module base; export

[Bug c++/115798] New: [15 Regression][modules] ICE when re-exporting a type exported from base module's GMF

2024-07-05 Thread m.cencora at gmail dot com via Gcc-bugs
IRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- $ cat base.cpp module; #include export module base; export { using ::int8_t; } export namespac

[Bug c++/115798] [15 Regression][modules] ICE when re-exporting a type exported from base module's GMF

2024-07-05 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115798 --- Comment #1 from m.cencora at gmail dot com --- Also this is specific to types exported from GMF, if type is declared directly in named module it works fine, i.e. $ cat base.cpp export module base; export { using int8_t = signed char

[Bug c++/115798] [15 Regression][modules] ICE when re-exporting a type exported from base module's GMF

2024-07-05 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115798 --- Comment #2 from m.cencora at gmail dot com --- (In reply to m.cencora from comment #1) > Also this is specific to types exported from GMF, if type is declared > directly in named module it works fine, i.e. > > $ cat base.c

[Bug c++/117293] New: SFINAE in class partial specialization "leaks" its side-effects

2024-10-25 Thread m.cencora at gmail dot com via Gcc-bugs
ty: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: m.cencora at gmail dot com Target Milestone: --- It seems like the deprecation warning is kept even if triggered due to failed substitution in context of class partial speciali

[Bug c++/117293] SFINAE in class partial specialization "leaks" its side-effects

2024-10-25 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117293 --- Comment #3 from m.cencora at gmail dot com --- I think it should be marked rejects-valid because it makes valid program ill-formed if compiled with -Werror. The problematic diagnostic is user-defined but in code that is never reached, so

[Bug c++/117293] SFINAE in class partial specialization "leaks" its side-effects

2024-10-25 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117293 --- Comment #5 from m.cencora at gmail dot com --- > I'd say that warning is not expected, because user's code didn't (directly > or indirectly) call the deprecated constructor. Or to state it differently: user calls

[Bug c++/117293] SFINAE in class partial specialization "leaks" its side-effects

2024-10-25 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117293 --- Comment #6 from m.cencora at gmail dot com --- Another argument for not showing the deprecation is that if I change: string a; to const string a; I don't get any deprecation warnings, but only for gcc-11+. This means that int

[Bug c++/117293] SFINAE in class partial specialization "leaks" its side-effects

2024-10-25 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117293 --- Comment #4 from m.cencora at gmail dot com --- (In reply to Andrew Pinski from comment #2) > (In reply to Andrew Pinski from comment #1) > > I am not sure this is related to SFINAE though. > > > > Rather it is in a

[Bug c++/117293] SFINAE in class partial specialization "leaks" its side-effects

2025-02-14 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117293 --- Comment #8 from m.cencora at gmail dot com --- (In reply to Patrick Palka from comment #7) > Substituting U=string into overload_set::type during > overload resolution certainly has the side effect of instantiating that > class

[Bug c++/118951] __FILE__ inserts the filename as array, __builtin_FILE as pointer

2025-02-20 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118951 m.cencora at gmail dot com changed: What|Removed |Added CC||m.cencora at gmail dot com

[Bug libstdc++/120160] Implicitly import std if standard library header is included

2025-05-08 Thread m.cencora at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120160 m.cencora at gmail dot com changed: What|Removed |Added CC||m.cencora at gmail dot com

<    1   2