[Bug c++/48379] -Wdouble-promotion warns for promotion by varargs

2025-03-16 Thread adam.f.badura at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48379 Adam Badura changed: What|Removed |Added CC||adam.f.badura at gmail dot com

[Bug c++/113051] New: -Wformat-signedness wrongly triggers for values from template arguments

2023-12-17 Thread adam.f.badura at gmail dot com via Gcc-bugs
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: adam.f.badura at gmail dot com Target Milestone: --- Consider sample code (https://godbolt.org/z/7T3vGefEq): ``` #include #include template auto foo() { return std::printf

[Bug c++/111087] -Wnonnull issued for std::array of zero size when under C++20

2023-08-21 Thread adam.f.badura at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111087 --- Comment #9 from Adam Badura --- Is there any option to improve the warning so that it is not generated in cases that are valid. I mean, to make it flow-dependent? How it works now? What it takes into account and how to phrase the code to av

[Bug c++/111087] -Wnonnull issued for std::array of zero size when under C++20

2023-08-21 Thread adam.f.badura at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111087 --- Comment #7 from Adam Badura --- So, the cases I described here _is_ a false-positive, however, an expected one. Do I understand this correctly? However, consider the code: class class1 { public: bool method1() const; }; bool

[Bug c++/111087] -Wnonnull issued for std::array of zero size when under C++20

2023-08-21 Thread adam.f.badura at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111087 --- Comment #5 from Adam Badura --- (In reply to Andrew Pinski from comment #3) > The warning is correct as tags.end() and tags.begin() will always be a > nullptr for std::array Yes. But what does it change? `std::lower_bound` gets an empty ra

[Bug c++/111087] -Wnonnull issued for std::array of zero size when under C++20

2023-08-20 Thread adam.f.badura at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111087 --- Comment #2 from Adam Badura --- (In reply to Andrew Pinski from comment #1) > Zero sized arrays are a gcc extension. The problem is with `std::array` rather than C-array. It seems to me `std::array` can have `0` size - it is not an extensio

[Bug c++/111087] New: -Wnonnull issued for std::array of zero size when under C++20

2023-08-20 Thread adam.f.badura at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: adam.f.badura at gmail dot com Target Milestone: --- At least for GCC 10.2 and 12.2, when using -std=c++20 I'm getting unexpected -Wnonnull in the following (simplified)

[Bug c/107802] -Wsuggest-attribute=format ignores [[gnu::format(...)]]

2022-11-22 Thread adam.f.badura at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107802 --- Comment #3 from Adam Badura --- Why is this marked as a duplicate of bug 98487? I have seen bug 98487 before reporting it. Furthermore, I experienced it while trying my code sample on the trunk version to see if the problem still exists. Ho

[Bug c++/107802] New: -Wsuggest-attribute=format ignores [[gnu::format(...)]]

2022-11-21 Thread adam.f.badura at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: adam.f.badura at gmail dot com Target Milestone: --- I checked the issue with GCC 10.2 and trunk as on Compiler Explorer using arguments -std=c++17 -O3 -Wall -Wextra -Wpedantic -Wsuggest

[Bug driver/91011] g++ -Q --help=warning,c++ outputs from C point of view

2019-06-27 Thread adam.f.badura at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91011 --- Comment #6 from Adam Badura --- (In reply to Jonathan Wakely from comment #5) > IMHO -x c++ should be sufficient to cause cc1plus to be used. I fully agree! However, it would mean the parameter would have to change its meaning (be extended)

[Bug c++/91011] g++ -Q --help=warning,c++ outputs from C point of view

2019-06-27 Thread adam.f.badura at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91011 --- Comment #4 from Adam Badura --- (In reply to Adam Badura from comment #3) > (In reply to Vladislav Ivanishin from comment #1) > > > > Is there any workaround for versions older than trunk? > > > > > > Using the executable for the appropria

[Bug c++/91011] g++ -Q --help=warning,c++ outputs from C point of view

2019-06-26 Thread adam.f.badura at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91011 --- Comment #3 from Adam Badura --- (In reply to Vladislav Ivanishin from comment #1) > > Is there any workaround for versions older than trunk? > > > Using the executable for the appropriate language frontend directly: > > `gcc --print-file-

[Bug c++/91011] New: g++ -Q --help=warning,c++ outputs from C point of view

2019-06-26 Thread adam.f.badura at gmail dot com
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: adam.f.badura at gmail dot com Target Milestone: --- My g++ -v outputs > Using built-in specs. > COLLECT_GCC=g++ > COLLECT_LTO_WRAPPER=/opt/gcc/x86_64/7.3.0a-1/libexec/gcc/x86_64-redhat-linux/7.3.0/lt