[Bug target/121025] New: [7.0 Regression] macOS ld sysroot delegation breaks libtool

2025-07-10 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121025 Bug ID: 121025 Summary: [7.0 Regression] macOS ld sysroot delegation breaks libtool Product: gcc Version: 15.1.1 Status: UNCONFIRMED Severity: normal

[Bug target/120641] Parameter passing warning from libstdc++ header

2025-06-16 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120641 --- Comment #8 from Pierre Ossman --- It seems strange to make life difficult for all ARM users, just to warn anyone that might potentially use GCC 6 and GCC 15 at the same time. Can we make sure that flag is the default in our build of the com

[Bug target/120641] Parameter passing warning from libstdc++ header

2025-06-13 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120641 --- Comment #5 from Pierre Ossman --- Created attachment 61631 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61631&action=edit GestureHandler.cxx.ii (xz compressed) Preprocessed output as the result of this run: > arm-none-linux-gnueabi

[Bug target/120641] Parameter passing warning from libstdc++ header

2025-06-13 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120641 --- Comment #4 from Pierre Ossman --- The error didn't indicate anything in our code, so I assumed this was entirely a standard library issue. The file in question is this one: https://github.com/TigerVNC/tigervnc/blob/master/vncviewer/Gesture

[Bug target/120641] Parameter passing warning from libstdc++ header

2025-06-12 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120641 --- Comment #2 from Pierre Ossman --- It's problematic when you are trying to adopt a "no warnings" approach to your development. This severely undermines that, as you train the developers back in to ignoring warning messages. It also seems exc

[Bug c++/120641] New: Parameter passing warning from libstdc++ header

2025-06-12 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120641 Bug ID: 120641 Summary: Parameter passing warning from libstdc++ header Product: gcc Version: 15.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component

[Bug target/60428] non-exception (e.g. C) ARM Linux programs depend on libgcc_s

2025-06-10 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60428 --- Comment #4 from Pierre Ossman --- Any updates on this? Still seems to be needed for gcc 15.

[Bug target/66587] -no_compact_unwind is dropped for -nodefaultlibs/-nostdlib

2025-06-10 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66587 Pierre Ossman changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug other/54750] conflicting float.h on windows using mingw

2025-05-23 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54750 Pierre Ossman changed: What|Removed |Added CC||ossman at cendio dot se --- Comment #1 f

[Bug c/120416] New: unreachable() missing on win32, but not win64

2025-05-23 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120416 Bug ID: 120416 Summary: unreachable() missing on win32, but not win64 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component:

[Bug target/110998] Inconsistent -Wformat warnings issued for %I64d

2025-04-25 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110998 Pierre Ossman changed: What|Removed |Added CC||ossman at cendio dot se --- Comment #1

[Bug other/66300] GCC_ENABLE_PLUGINS references undefined variables, breaking configure

2025-04-08 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66300 Pierre Ossman changed: What|Removed |Added Version|5.1.0 |14.2.0 --- Comment #2 from Pierre Ossman

[Bug c++/114571] -Wzero-as-null-pointer-constant does not complain about NULL

2024-10-10 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571 --- Comment #5 from Pierre Ossman --- That may be, but -Wzero-as-null-pointer-constant is documented as facilitating conversion to "nullptr", which means it definitely should be complaining about NULL, since that might not be the same thing. Co

[Bug c++/56556] Wshadow warns for private members in base classes

2024-09-27 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56556 Pierre Ossman changed: What|Removed |Added CC||ossman at cendio dot se --- Comment #5 f

[Bug c++/78147] The -Wshadow warning is too aggressive with constructor parameters

2024-09-27 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78147 Pierre Ossman changed: What|Removed |Added CC||ossman at cendio dot se --- Comment #9 f

[Bug c++/115664] -Wnonnull-compare breaks templated methods

2024-07-01 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115664 --- Comment #9 from Pierre Ossman --- Thank you! That worked nicely!

[Bug c++/115664] -Wnonnull-compare breaks templated methods

2024-06-27 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115664 --- Comment #6 from Pierre Ossman --- Is there a cleaner way to can work around this than duplicating the affected methods? I tried adding a #pragma, but that breaks older versions of gcc that don't have -Wnonnull-compare.

[Bug c++/115664] New: -Wnonnull-compare breaks templated methods

2024-06-26 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115664 Bug ID: 115664 Summary: -Wnonnull-compare breaks templated methods Product: gcc Version: 13.3.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug c++/114571] -Wzero-as-null-pointer-constant does not complain about NULL

2024-04-03 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571 --- Comment #3 from Pierre Ossman --- And another odd case; gcc 5 complains about this: > const char *a; > a = NULL; but not: > const char *a = NULL; gcc 13 complains about neither, and clang about both.

[Bug c++/114573] -Wzero-as-null-pointer-constant complains on enum with explicit cast

2024-04-03 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114573 --- Comment #2 from Pierre Ossman --- Indeed. It is part of an effort to have a more modern C++ style in TigerVNC. One item was preferring nullptr over NULL, and this issue became an obstacle there. Right now, we did a #pragma, but if there is

[Bug c++/114571] -Wzero-as-null-pointer-constant does not complain about NULL

2024-04-03 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571 --- Comment #2 from Pierre Ossman --- Found another case that neither gcc 5, gcc 13, nor clang complain about for some odd reason: > assert(thing == NULL); All three complain about: > assert(thing == 0); Not sure what's going on here.

[Bug c++/114573] New: -Wzero-as-null-pointer-constant complains on enum with explicit cast

2024-04-03 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114573 Bug ID: 114573 Summary: -Wzero-as-null-pointer-constant complains on enum with explicit cast Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

[Bug c++/114571] -Wzero-as-null-pointer-constant does not complain about NULL

2024-04-03 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571 --- Comment #1 from Pierre Ossman --- Hmm.. I found bug 77513, and r9-873. So I guess this is intentional? This makes the warning somewhat pointless. We want to make sure developers standardise on nullptr, both for style and since the behaviour

[Bug c++/114571] New: -Wzero-as-null-pointer-constant does not complain about NULL

2024-04-03 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571 Bug ID: 114571 Summary: -Wzero-as-null-pointer-constant does not complain about NULL Product: gcc Version: 13.2.1 Status: UNCONFIRMED Severity: normal

[Bug objc/108743] -fconstant-cfstrings not supported

2023-02-10 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108743 --- Comment #5 from Pierre Ossman --- Could you consider adding -fconstant-cfstrings as an alias? It would make life easier for making build systems compiler agnostic.

[Bug objc/108743] -fconstant-cfstrings not supported

2023-02-10 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108743 --- Comment #4 from Pierre Ossman --- I am indeed trying to compile for macOS. Specifically Qt5, which is designed with just Xcode in mind.

[Bug objc/108743] -fconstant-cfstrings not supported

2023-02-09 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108743 --- Comment #2 from Pierre Ossman --- Great news. And that is the same thing as clang's -fconstant-cfstrings? Unfortunately, I couldn't see -mconstant-cfstrings in gcc's documentation, but I may be looking in the wrong place.

[Bug objc/108743] New: -fconstant-cfstrings not supported

2023-02-09 Thread ossman at cendio dot se via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108743 Bug ID: 108743 Summary: -fconstant-cfstrings not supported Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: objc