[Bug c++/94492] New: no way to silence -Wdeprecated-copy for aggregates

2020-04-05 Thread nok.raven at gmail dot com
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- There is no way to silence the warning without making a type non-aggregate. A simplified case from Boost.Proto: #pragma GCC diagnostic push

[Bug c++/95825] New: [7/8/9/10/11 Regression] boost::optional -Wuninitialized

2020-06-22 Thread nok.raven at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- #include boost::optional get() { return {}; } boost::optional foo() { return get(); } // g++ -O3 -Wall

[Bug tree-optimization/96166] New: [10/11 Regression] -O3/-ftree-slp-vectorize turns ROL into a mess

2020-07-11 Thread nok.raven at gmail dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- inline void swap(int &x, int &y) { int tmp = x; x = y; y = tmp; } void bar(int (&x)[2])

[Bug tree-optimization/96167] New: fails to detect ROL pattern in simple case, but succeeds when operand goes through memcpy

2020-07-11 Thread nok.raven at gmail dot com
Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- inline void swap(int &x, int &y) { int tmp = x; x = y; y = tmp; } void foo(in

[Bug c++/92145] New: -Wdeprecated-copy false-positive when inheriting base assignment operators

2019-10-17 Thread nok.raven at gmail dot com
: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- // https://godbolt.org/z/UAc5tq struct base { base() { } base(const base&) { }

[Bug c++/92399] New: Rejects valid: reading of an inactive union member that shares common initial sequence with the active on

2019-11-06 Thread nok.raven at gmail dot com
: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- The wording is in [class.union]/1 and [class.mem]/25

[Bug c++/92399] Rejects valid: reading of an inactive union member that shares common initial sequence with the active on

2019-11-06 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92399 Nikita Kniazev changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/92434] New: noexcept couldn't be deduced in function template

2019-11-09 Thread nok.raven at gmail dot com
ormal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- template void foo(void(*f)() noexcept(b)); void f(); void bar() { foo(&f); } g++ foo.cpp -std=c++17 : In function 'v

[Bug c++/92459] New: out of class method definition did not match (when declaration contains expression that uses in class defined enum)

2019-11-11 Thread nok.raven at gmail dot com
: 10.0 Status: UNCONFIRMED Keywords: rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- template struct S {}; struct X

[Bug c++/92539] New: [8/9/10 Regression] -Warray-bounds false positive (loop unroll?)

2019-11-15 Thread nok.raven at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- static bool ischar(int ch) { return (0 == (ch & ~0xff) || ~0 == (ch | 0xff)) != 0; } static bool

[Bug c++/92434] noexcept couldn't be deduced in function template

2020-01-30 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92434 --- Comment #5 from Nikita Kniazev --- > but does [temp.deduct] actually require that this works? Judging by CWG 2355 it does not.

[Bug c++/56665] -O2 with -fno-strict-aliasing makes boost::spirit::classic::assign_a not working

2019-01-27 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56665 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug rtl-optimization/89155] New: Suboptimal code generation for SSE intrinsics based rsqrt

2019-02-01 Thread nok.raven at gmail dot com
Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Target: x86_64 #include float rsqrtf_a(float x) { return _mm_cvtss_f32

[Bug rtl-optimization/89198] New: GCC generates/fails to optimize unnecessary sign extension instruction

2019-02-04 Thread nok.raven at gmail dot com
-optimization Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Target: x86_64 GCC generates/fails to optimize unnecessary sign

[Bug tree-optimization/91213] New: Missed optimization: (sub X Y) -> (xor X Y) when Y <= X and isPowerOf2(X + 1)

2019-07-19 Thread nok.raven at gmail dot com
verity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Proof https://rise4fun.com/Alive/Xr3 unsigned foo(unsigned x) { if (x > 31) __builtin_un

[Bug c++/89381] New: Implicit copy constructor cannot be generated after unrelated class definition

2019-02-17 Thread nok.raven at gmail dot com
: diagnostic, needs-reduction, rejects-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- For some reason `bar` makes `foo` not copy-constructible. It

[Bug preprocessor/60875] `_Pragma("message \"foo\")"` doesn't work in expression contexts.

2019-02-28 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60875 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug regression/89733] New: [7/8/9 Regression] False positive -Wuninitialized in C++14+ mode

2019-03-15 Thread nok.raven at gmail dot com
Severity: normal Priority: P3 Component: regression Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Host: x86_64 Target: x86_64 Hello, The -Wuninitialized warning comes from

[Bug regression/89733] [7/8/9 Regression] False positive -Wuninitialized in C++14+ mode

2019-03-18 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89733 --- Comment #2 from Nikita Kniazev --- Created attachment 45990 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45990&action=edit preprocessed repro

[Bug middle-end/86912] Function pointer imposes an optimization barrier

2019-03-24 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86912 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug target/89809] New: movzwl is not utilized when uint16_t is loaded with bit-shifts (while memcpy does)

2019-03-24 Thread nok.raven at gmail dot com
Keywords: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Host: x86_64 Target: x86_64 #include #include

[Bug tree-optimization/89810] New: Suboptimal codegen: integer load/assemble from in-register array of uint8_t

2019-03-24 Thread nok.raven at gmail dot com
: missed-optimization Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Clang optimizes it perfectly, while GCC does byte-per-byte assemble

[Bug target/89811] New: uint32_t load is not recognized if shifts are done in a fixed-size loop

2019-03-24 Thread nok.raven at gmail dot com
-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Host: x86_64 Target: x86_64 I was expecting that fixed-size

[Bug target/89822] New: self mov on x86_64 and not optimized-out sub on ARM/ARM64 in a jump table switch

2019-03-25 Thread nok.raven at gmail dot com
: missed-optimization Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Host: x86_64 Target: x86_64/ARM/ARM64 Created

[Bug regression/89733] [7/8/9 Regression] False positive -Wuninitialized in C++14+ mode

2019-03-26 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89733 --- Comment #4 from Nikita Kniazev --- So the warning triggers intentionally in copy/move even if the value actually not read anywhere in the user code?

[Bug regression/89733] [7/8/9 Regression] False positive -Wuninitialized in C++14+ mode

2019-03-26 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89733 --- Comment #6 from Nikita Kniazev --- I understand. I though that -Wuninitialized should not produce false positives and that's a main difference between it and -Wno-maybe-uninitialized. The warning does not go away and does not change to -Wno-

[Bug rtl-optimization/86525] [missed-optimization] extraneous instruction emitted in switch converted to look-uptable load

2019-03-27 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86525 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug c++/89976] New: missing uninitialized warning: laundering via passing object through a function

2019-04-04 Thread nok.raven at gmail dot com
: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- // case 1 - https://godbolt.org/z/02zu_3 struct X { int x, y; X() : y(0) {} }; X

[Bug regression/89733] [7/8/9 Regression] -Wuninitialized false positive with unclear message pointing to a class name

2019-04-07 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89733 Nikita Kniazev changed: What|Removed |Added Summary|[7/8/9 Regression] False|[7/8/9 Regression] |p

[Bug tree-optimization/90087] New: Suboptimal codegen for x < 0 ? x - INT_MIN : x

2019-04-14 Thread nok.raven at gmail dot com
mal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Target: x86_64,AArch64 int foo(int x) { return x < 0 ? x - INT_MIN : x; }

[Bug target/90088] New: 3 ops LEA should be avoided on Intel CPUs

2019-04-14 Thread nok.raven at gmail dot com
Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Target: Intel x86 Originally I filed a bug report to LLVM about int foo(int x) { return (x << 1) | 1; } But got an answered that 3 ops LEA is intenti

[Bug target/90088] 3 ops LEA should be avoided on Intel CPUs

2019-04-14 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90088 --- Comment #2 from Nikita Kniazev --- > I could see it being useful for -Os case. Yes, and I also was confirmed that it is a bug that Clang with -Os avoids it.

[Bug preprocessor/60875] `_Pragma("message \"foo\")"` doesn't work in expression contexts.

2019-04-20 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60875 --- Comment #6 from Nikita Kniazev --- > Those pragmas are all extensions, so the standard doesn't cover them. There was a Clang bug report recently with a pretty much same code I had posted previously and Clang developers said that it is ill-fo

[Bug c++/89976] missing uninitialized warning: laundering via passing object through a function

2019-07-05 Thread nok.raven at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89976 --- Comment #2 from Nikita Kniazev --- The same warning as when the object is constructed inside the main function: int main() { XorYorZ x; return x.x; } Also, the warning is not triggered in C++17+ mode with: XorYorZ foo() { retur

[Bug c++/87531] New: [8/9 Regression] assignment operator does nothing if performed as a call via operator=

2018-10-05 Thread nok.raven at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- The regression appeared after 7.3.0 and not later than 8.1.0. I do not have 8.0.0 to test it. https://godbolt.org

[Bug c++/87570] New: Rejects valid alias template usage (as a type pack size requirement)

2018-10-09 Thread nok.raven at gmail dot com
-valid Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- MWE: template using limit_argnum = T; template struct tuple { template tuple

[Bug c++/99331] New: -Wconversion false-positive in immidiate context

2021-03-01 Thread nok.raven at gmail dot com via Gcc-bugs
Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- template struct X {}; template X foo(); g++ -Wconversion -Werror src.cpp :2:22: error: conversion from 'long unsigned int' to

[Bug c++/99331] [8/9/10/11 Regression] -Wconversion false-positive in immediate context

2021-03-01 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99331 --- Comment #3 from Nikita Kniazev --- This one most likely has the same root problem: template struct X {}; template struct foo { using t = X; }; :3:26: error: conversion from 'long unsigned int' to 'int' may change value [-Werror=conversion

[Bug c++/99331] [8/9/10 Regression] -Wconversion false-positive in immediate context

2021-03-26 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99331 --- Comment #7 from Nikita Kniazev --- The fix silenced the true warning (though it was saying 'may') in these: template struct X {}; template X foo(); int x = sizeof(foo()); template struct X {}; template struct foo { using t = X; }; foo

[Bug c++/99795] New: -Wnarrowing/-Woverflow false-negative in constant expression in undeduced context

2021-03-26 Thread nok.raven at gmail dot com via Gcc-bugs
Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com CC: jason at redhat dot com, mpolacek at gcc dot gnu.org Target Milestone: --- template struct

[Bug target/100021] New: [9/10/11 Regression] std::clamp unprofitable vectorization on -march=nehalem/.../broadwell

2021-04-10 Thread nok.raven at gmail dot com via Gcc-bugs
Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- //#include namespace std { template constexpr const _Tp& clamp(const _Tp& __val, c

[Bug target/100021] [9/10/11 Regression] std::clamp unprofitable vectorization on -march=nehalem/.../broadwell

2021-04-12 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100021 Nikita Kniazev changed: What|Removed |Added Resolution|--- |INVALID Status|WAITING

[Bug libstdc++/100243] New: [10 Regression] invalid use of incomplete type 'std::__detail::__iter_traits >' {aka 'struct std::indirectly_readable_traits'}

2021-04-23 Thread nok.raven at gmail dot com via Gcc-bugs
Product: gcc Version: 10.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- // g++-10 -std=c++2a #

[Bug tree-optimization/93721] swapping adjacent scalars could be more efficient

2021-02-13 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93721 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug c++/88136] -Wdeprecated-copy is draconian and shouldn't be in -Wall

2021-02-25 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88136 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug rtl-optimization/99305] New: [11 Regression] range condition simplification after inlining

2021-02-27 Thread nok.raven at gmail dot com via Gcc-bugs
Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- bool foo(char c) { return c >= '0' && c <= '9'; } bool bar(char c) { return c != &#x

[Bug c++/100608] New: [10/11/12 Regression] -Wshadow=compatible-local false positive: function local type declaration shadows variable of different type

2021-05-14 Thread nok.raven at gmail dot com via Gcc-bugs
Version: 10.3.1 Status: UNCONFIRMED Keywords: diagnostic Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- template class X

[Bug tree-optimization/100857] New: Simple common code sinking is not performed

2021-06-01 Thread nok.raven at gmail dot com via Gcc-bugs
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- void bar(int); void foo(bool f) { if (f) { bar(1); } else { bar(2); } } ; GCC foo(bool

[Bug tree-optimization/100858] New: Simple common code hoisting is not performed

2021-06-01 Thread nok.raven at gmail dot com via Gcc-bugs
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- void bar(); int foo(bool f) { if (f) { bar(); return 1; } else { bar

[Bug tree-optimization/100858] Simple common code hoisting is not performed

2021-06-02 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100858 --- Comment #2 from Nikita Kniazev --- (In reply to Richard Biener from comment #1) > That's really a duplicate of 100858 - this case can be handled by sinking as > well > since we "sink" the return. Make it > > void bar(); > > int foo(bool f

[Bug c++/94492] no way to silence -Wdeprecated-copy for aggregates

2021-06-02 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94492 --- Comment #2 from Nikita Kniazev --- Could this be backported? The issue affects every release with -Wdeprecated-copy, which are GCC 9+.

[Bug rtl-optimization/108992] New: Regression: Branch direction canonicalization leads to pointless tail duplication / CSE/sinking by inverting branch

2023-03-02 Thread nok.raven at gmail dot com via Gcc-bugs
: 6.0 Status: UNCONFIRMED Keywords: missed-optimization Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- There are two

[Bug rtl-optimization/108992] Regression: Branch direction canonicalization leads to pointless tail duplication / CSE/sinking by inverting branch

2023-03-02 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108992 --- Comment #2 from Nikita Kniazev --- > Why do you think this is a bug? > I don't see anything wrong with the newer versions of gcc. > Duplicating the basic blocks is done on purpose for speed reasons. I understand that removing diamonds is do

[Bug middle-end/108992] Regression: Branch direction canonicalization leads to pointless tail duplication / CSE/sinking by inverting branch

2023-03-02 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108992 --- Comment #6 from Nikita Kniazev --- > Did you see this in real code or you just noticed this while looking at code > generation? If you mean do I have any benchmark - unfortunately no. I noticed it for a while by poking different code to co

[Bug tree-optimization/108997] GCC prediction on bool comparisons seems wrong

2023-03-02 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108997 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com

[Bug tree-optimization/108997] GCC prediction on bool comparisons seems wrong

2023-03-02 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108997 --- Comment #3 from Nikita Kniazev --- For cond == 789 if (cond_2(D) == 789) goto ; [20.24%] else goto ; [79.76%] For cond != 789 if (cond_2(D) != 789) goto ; [48.88%] else goto ; [51.12%]

[Bug c++/92145] -Wdeprecated-copy false-positive when inheriting base assignment operators

2021-11-24 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92145 --- Comment #3 from Nikita Kniazev --- (In reply to Marek Polacek from comment #2) > Fixed? It is fixed on trunk but still presented in every release (since the fix landed 9.4 and 11.2 were released). I assume it was not backported, could you pl

[Bug ipa/101813] New: -O3 does worse at constant folding than -O2

2021-08-07 Thread nok.raven at gmail dot com via Gcc-bugs
Priority: P3 Component: ipa Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- #include #include using opts = boost::optional; struct foo { foo(opts x) : b(x), c

[Bug c++/101537] -Wconversion false positive in ternary

2021-08-08 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101537 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com

[Bug libstdc++/101923] std::function's move ctor is slower than the copy one for empty source objects

2021-08-15 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101923 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com

[Bug c++/93016] erroneous new (nothrow_t) still throws an exception

2023-03-19 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93016 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com --- Comment

[Bug libstdc++/106477] With -fno-exception operator new(nothrow) aborts instead of returning null

2023-03-19 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106477 Nikita Kniazev changed: What|Removed |Added CC||nok.raven at gmail dot com

[Bug target/114775] New: on mingw __attribute__ ((__format__ (__printf__, ...))) doesn't recognize C99 specifiers

2024-04-18 Thread nok.raven at gmail dot com via Gcc-bugs
IRMED Keywords: diagnostic Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: nok.raven at gmail dot com Target Milestone: --- Target: *-w64-mingw32 #define ATTRIBUTE_PRINTF

[Bug target/114775] on mingw __attribute__ ((__format__ (__printf__, ...))) doesn't recognize C99 specifiers

2024-04-18 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114775 --- Comment #5 from Nikita Kniazev --- > So there is mingw_printf and gnu_printf attributes for mingw because at one > point %ll didn't exist for mingw and nobody has updated it since then. Do you mean that binutils and [other code out there](

[Bug target/114775] on mingw __attribute__ ((__format__ (__printf__, ...))) doesn't recognize C99 specifiers

2024-04-18 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114775 --- Comment #7 from Nikita Kniazev --- (In reply to Andrew Pinski from comment #6) > (In reply to Nikita Kniazev from comment #5) > > > So there is mingw_printf and gnu_printf attributes for mingw because at > > > one point %ll didn't exist for

[Bug target/114775] on mingw __attribute__ ((__format__ (__printf__, ...))) doesn't recognize C99 specifiers

2024-04-18 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114775 --- Comment #9 from Nikita Kniazev --- Ok, is there at least an option to build GCC so it defaults __printf__ to gnu_printf? Defaulting __printf__ to ms_printf on UCRT is wrong (every OS without UCRT is already EOL).

[Bug target/114775] on mingw __attribute__ ((__format__ (__printf__, ...))) doesn't recognize C99 specifiers

2024-04-18 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114775 Nikita Kniazev changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug target/114775] on mingw __attribute__ ((__format__ (__printf__, ...))) doesn't recognize C99 specifiers

2024-04-18 Thread nok.raven at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114775 --- Comment #13 from Nikita Kniazev --- (In reply to Andrew Pinski from comment #12) > The reality is ms_printf most likely should just include z and ll support > instead since they are supported now: > https://learn.microsoft.com/en-us/cpp/c-r