[Bug libstdc++/54172] [4.7/4.8 Regression] __cxa_guard_acquire thread-safety issue

2012-08-29 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54172 James Y Knight foom at fuhm dot net changed: What|Removed |Added CC||foom at fuhm dot net

[Bug libstdc++/54075] [4.7.1] unordered_map insert 3x slower than 4.6.2

2012-11-03 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54075 James Y Knight foom at fuhm dot net changed: What|Removed |Added CC||foom at fuhm

[Bug c++/53356] New: ICE in verify_gimple_stmt, at tree-cfg.c:4258

2012-05-14 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53356 Bug #: 53356 Summary: ICE in verify_gimple_stmt, at tree-cfg.c:4258 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal

[Bug c++/53364] New: [4.7/4.8 Regression] Wrong code generation

2012-05-15 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53364 Bug #: 53364 Summary: [4.7/4.8 Regression] Wrong code generation Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal

[Bug c++/53364] [4.7/4.8 Regression] Wrong code generation

2012-05-15 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53364 --- Comment #1 from foom at fuhm dot net 2012-05-16 04:10:59 UTC --- Asm generated. Note that at no point is anything ever actually written to the stack, only read from it: main: 0:83 3d 00 00 00 00 09 cmpl $0x9,0x0

[Bug c++/53364] [4.7/4.8 Regression] Wrong code generation

2012-05-15 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53364 --- Comment #3 from foom at fuhm dot net 2012-05-16 04:28:21 UTC --- Does -fno-tree-vrp fix the issue? Nope, g++ -O2 -fno-tree-vrp -c test.cpp is no different than without.

[Bug c++/54170] Call to lambda elided

2013-07-09 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54170 James Y Knight foom at fuhm dot net changed: What|Removed |Added CC||foom at fuhm dot net

[Bug c++/41863] New: [4.5 Regression] segfault with sizeof in template parameter

2009-10-28 Thread foom at fuhm dot net
parameter Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: foom at fuhm dot net GCC host triplet: x86_64-linux

[Bug middle-end/41290] [4.5 regression] C++ - libdirac don't want to compile

2009-10-29 Thread foom at fuhm dot net
--- Comment #5 from foom at fuhm dot net 2009-10-30 02:42 --- An error very much like this is also causing a bunch of files in my program to fail to compile with 4.5 with -O1 and above. I was unable to reduce a simple test case from my (private) code, though: many changes that seem like

[Bug middle-end/41290] [4.5 regression] ICE: edge points to wrong declaration

2010-01-11 Thread foom at fuhm dot net
--- Comment #13 from foom at fuhm dot net 2010-01-12 06:27 --- The crash is still present for my code. I'm using: g++ (Debian 20091228-2) 4.5.0 20091228 (experimental) [trunk revision 155486] on AMD64. Passing -fno-ipa-cp also makes the bug disappear for me. But apparently r154673 did

[Bug c++/42797] New: call of overloaded 'allocator()' is ambiguous

2010-01-18 Thread foom at fuhm dot net
Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: foom at fuhm dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42797

[Bug c++/42797] call of overloaded 'allocator()' is ambiguous

2010-01-18 Thread foom at fuhm dot net
--- Comment #1 from foom at fuhm dot net 2010-01-19 06:15 --- Error also occurs with: g++ -O1 -fipa-sra -g -std=c++0x -c test.cpp -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42797

[Bug middle-end/41290] [4.5 regression] ICE: edge points to wrong declaration

2010-02-10 Thread foom at fuhm dot net
--- Comment #15 from foom at fuhm dot net 2010-02-10 23:24 --- Nope, adding -fno-indirect-inlining has no effect. I'm now using: g++-4.5 (Debian 4.5-20100202-1) 4.5.0 20100202 (experimental) [trunk revision 156452] Problem still occurs, -fno-ipa-cp still makes it go away. -- http

[Bug middle-end/41290] [4.5 regression] ICE: edge points to wrong declaration

2010-02-12 Thread foom at fuhm dot net
--- Comment #17 from foom at fuhm dot net 2010-02-12 21:46 --- Thanks, I will try doing that. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41290

[Bug middle-end/41290] [4.5 regression] ICE: edge points to wrong declaration

2010-03-10 Thread foom at fuhm dot net
--- Comment #18 from foom at fuhm dot net 2010-03-10 20:32 --- Sorry for the extreme delay in responding. I can confirm that applying that patch on top of: gcc-4.5 (Debian 4.5-20100227-1) 4.5.0 20100227 (experimental) [trunk revision 157109] *does* make my issue go away, and my program

[Bug libstdc++/49561] [C++0x] std::list::size complexity

2011-10-06 Thread foom at fuhm dot net
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49561 foom at fuhm dot net changed: What|Removed |Added CC||foom at fuhm dot net --- Comment

[Bug c++/44487] New: pair of references doesn't work in c++0x mode

2010-06-09 Thread foom at fuhm dot net
: gcc Version: 4.5.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: foom at fuhm dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44487

[Bug libstdc++/45060] New: Wreorder warning in bits/hashtable.h

2010-07-24 Thread foom at fuhm dot net
: unassigned at gcc dot gnu dot org ReportedBy: foom at fuhm dot net http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45060

[Bug c++/65945] C++ alignment of nullptr_t is 1 and might cause unaligned stores to the frame

2015-06-04 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65945 --- Comment #11 from James Y Knight foom at fuhm dot net --- As far as I can tell, the C++ ABI discussion, http://comments.gmane.org/gmane.comp.lang.c++.abi/265 concluded that alignof(nullptr_t) should be alignof(void*) already. Any chance

[Bug libstdc++/66438] New: libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-05 Thread foom at fuhm dot net
: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- If you compile this program with GCC 4.9, but you have libstdc++ version 5.1 installed on your system. (E.g., this is the case

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 James Y Knight foom at fuhm dot net changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 --- Comment #9 from James Y Knight foom at fuhm dot net --- What good is having special code to allow linking compatibility, if the program then can't work anyways? Isn't that anti-useful? I didn't realise you were the maintainer and knew

[Bug libstdc++/66438] libstdc++ 5.1 broke binary compat with old code using std::error_category

2015-06-06 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66438 James Y Knight foom at fuhm dot net changed: What|Removed |Added CC||doko at gcc dot

[Bug c++/65945] C++ alignment of nullptr_t is 1 and might cause unaligned stores to the frame

2015-06-19 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65945 --- Comment #12 from James Y Knight foom at fuhm dot net --- Since this would at least theoretically be a c++11 ABI change -- although it seems likely not to impact the ABI of most actual software -- it seems like it'd be a really good idea

[Bug c++/65945] C++ alignment of nullptr_t is 1 and might cause unaligned stores to the frame

2015-05-22 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65945 James Y Knight foom at fuhm dot net changed: What|Removed |Added CC||foom at fuhm dot

[Bug target/46942] x86_64 parameter passing unnecessary sign/zero extends

2015-09-16 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46942 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #10

[Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences

2018-06-12 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005 --- Comment #10 from James Y Knight --- I suppose since it doesn't affect most common platforms, nobody's noticed the brokenness yet? ARM is probably the most common architecture which is missing atomics on common CPU models, but when targeting

[Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences

2018-06-01 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005 --- Comment #7 from James Y Knight --- (In reply to Jim Wilson from comment #6) > On Thu, 2018-05-31 at 15:07 +0000, foom at fuhm dot net wrote: > > (But also, why doesn't it implement __atomic_add_fetch inline?) > > If you do

[Bug target/86005] [RISCV] Invalid intermixing of __atomic_* libcalls and inline atomic instruction sequences

2018-05-31 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86005 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #4

[Bug tree-optimization/61502] == comparison on "one-past" pointer gives wrong result

2018-05-03 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #24

[Bug c++/87521] [C++][ABI] Tail padding not reused for non POD struct with defaulted/deleted special member function as per Itanium ABI on x86-64

2018-11-15 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87521 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #5

[Bug c++/88115] New: Incorrect result from alignof in templates, if also using __alignof__.

2018-11-20 Thread foom at fuhm dot net
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- On both GCC 8.2 and "trunk" on godbolt (https://godbolt.org/z/ykszUZ) given the following program, compiled for x86 -m32,

[Bug libstdc++/88119] New: std::alignment_of returns wrong value (__alignof instead of alignof).

2018-11-20 Thread foom at fuhm dot net
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- std::alignment_of is currently defined based on "__alignof__", but according to the standard [meta.unary.prop.query],

[Bug c++/69560] x86_64: alignof(uint64_t) produces incorrect results with -m32

2018-11-20 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69560 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #24

[Bug libstdc++/89855] New: Inconsistent global namespace overload sets from #include

2019-03-27 Thread foom at fuhm dot net
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- In the following, I use the function "log" as an example, but this applies to effectively everything in cmath, and ::abs in cstdl

[Bug libstdc++/89855] Inconsistent global namespace overload sets from #include

2020-04-29 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89855 --- Comment #7 from James Y Knight --- Ugh, GCC doesn't wrap quoted text? Re-posting the quote from http://eel.is/c++draft/headers#5 without a quote marker... """ Except as noted in [library] through [thread] and [depr], the contents of each

[Bug libstdc++/89855] Inconsistent global namespace overload sets from #include

2020-04-29 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89855 --- Comment #6 from James Y Knight --- Someone has pointed out to me that the standard actually says "name", which I had internalized as meaning "declaration", but it doesn't. This arguably does make the GCC implementation non-compliant with the

[Bug libstdc++/88466] [C++17] Support std::hardware_destructive_interference_size and std:: hardware_constructive_interference_size

2020-03-18 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88466 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #7

[Bug target/95722] libatomic crashes on __atomic_load of const object

2020-06-17 Thread foom at fuhm dot net
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95722 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #1

[Bug libstdc++/97449] New: libstdc++ cannot be compiled with clang after 3427e31331677ca826c5588c87924214f7e5c54b

2020-10-15 Thread foom at fuhm dot net via Gcc-bugs
Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- After 3427e31331677ca826c5588c87924214f7e5c54b, "clang -std=c++17" (using libstdc++ headers), on a fil

[Bug c++/88115] Incorrect result from alignof in templates, if also using __alignof__.

2021-01-07 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88115 --- Comment #9 from James Y Knight --- Proposed patch posted for the itanium-cxx-abi: https://github.com/itanium-cxx-abi/cxx-abi/pull/115/files using the syntax: u * E And to Clang, to use that syntax: https://reviews.llvm.org/D93922 I

[Bug c++/88115] Incorrect result from alignof in templates, if also using __alignof__.

2020-11-14 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88115 --- Comment #6 from James Y Knight --- > c++: Change the mangling of __alignof__ [PR88115] The new mangling chosen for __alignof__(type) seems problematic, and I think this commit ought to be reverted until a new mangling scheme has been

[Bug c++/88115] Incorrect result from alignof in templates, if also using __alignof__.

2020-11-16 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88115 --- Comment #7 from James Y Knight --- I've created an ABI proposal against itanium abi, here: https://github.com/itanium-cxx-abi/cxx-abi/issues/112 I realized since writing my last comment here that ::= u [] # vendor extended type has been

[Bug target/98495] New: X86 _mm_extract_pi16 incorrectly sign extends result

2020-12-31 Thread foom at fuhm dot net via Gcc-bugs
Component: target Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- #include int test(__m64 a) { return _mm_extract_pi16 (a, 0); } Compiles to (x86_64 gcc, -O2): pextrw $0, %xmm0, %eax cwtl ret Which results

[Bug c++/98804] New: GCC misparses template in pack expansion as comparison

2021-01-23 Thread foom at fuhm dot net via Gcc-bugs
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net CC: richard-gccbugzilla at metafoo dot co.uk Target Milestone: --- GCC parses the following program (by Richard Smith) as `g` less-than `a` greater-than `(a)` instead of a call

[Bug target/98522] New: _mm_cvttps_pi32 and _mm_cvtps_pi32 raise spurious FP exceptions

2021-01-04 Thread foom at fuhm dot net via Gcc-bugs
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- This is a regression due to the MMX in SSE work in GCC10. As far as I can tell, it affects only these two functions. Example test, which

[Bug inline-asm/100953] Add memory clobbers just for reads or just for writes

2021-06-22 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100953 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #3

[Bug c++/88115] Incorrect result from alignof in templates, if also using __alignof__.

2021-01-29 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88115 --- Comment #10 from James Y Knight --- Seeing as GCC is now in Stage 4 before the next release, I'd like to ping this bug. Should the priority be upgraded? I think fixing this so that GCC doesn't use 'v111__alignof__' should be considered a

[Bug c++/55918] Stack partially unwound when noexcept causes call to std::terminate

2021-12-04 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55918 --- Comment #6 from James Y Knight --- I realize that my suggestion above could only solve _most_ of the problem -- e.g. the original example, where the noexcept function doesn't have a try/catch in it. In that original example, there's no

[Bug inline-asm/98096] Inconsistent operand numbering for asm goto with in-out operands

2022-01-05 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98096 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #7

[Bug c++/55918] Stack partially unwound when noexcept causes call to std::terminate

2021-11-14 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55918 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #5

[Bug libstdc++/104602] New: std::source_location::current uses cast from void*

2022-02-18 Thread foom at fuhm dot net via Gcc-bugs
Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- I'm working on implementing __builtin_source_location() in Clang (https://reviews.llvm.org/D120159). In testing it against the libstdc++ header, I ran into a minor

[Bug libstdc++/104602] std::source_location::current uses cast from void*

2022-02-21 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104602 --- Comment #4 from James Y Knight --- Yea that should work. Or even just `auto`.

[Bug c++/56958] Spurious set but not used variable warning in empty pack expansion

2022-02-01 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56958 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #6

[Bug tree-optimization/100038] -Warray-bound triggers false positives

2022-02-09 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100038 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #8

[Bug libstdc++/111351] constexpr std::string objects permitted to escape constant evaluation when SSO

2023-09-11 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111351 --- Comment #4 from James Y Knight --- vector and string are different in one key way: a zero-sized vector has no accessible storage, while a zero-sized string has 1 byte of readable storage -- the NUL terminator. Because of that, I don't think

[Bug libstdc++/111351] constexpr std::string objects permitted to escape constant evaluation when SSO

2023-09-12 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111351 --- Comment #5 from James Y Knight --- > Does using __builtin_is_constant_p on the union member not work? I've created a proof-of-concept patch for libc++ to support SSO strings during constant evaluation. It works. If everyone disagrees with

[Bug libstdc++/111351] New: constexpr std::string objects permitted to escape constant evaluation when SSO

2023-09-08 Thread foom at fuhm dot net via Gcc-bugs
: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: foom at fuhm dot net Target Milestone: --- In C++20, libstdc++ currently allows an std::string instance to escape from constant evaluation to runtime, as long

[Bug libstdc++/111351] constexpr std::string objects permitted to escape constant evaluation when SSO

2023-09-26 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111351 --- Comment #7 from James Y Knight --- On the libc++ side, a suggestion was given that instead of making this an _error_, we could instead emit a warning if "a constexpr or constinit object is a basic_string or contains a basic_string

[Bug c++/36685] clarify/diagnose use of weak constant

2022-05-25 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36685 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #4

[Bug c++/36685] clarify/diagnose use of weak constant

2022-05-25 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36685 --- Comment #5 from James Y Knight --- (oops submitted commit by mistake, continuing...) Strangely, it appears that Clang and GCC both have odd behaviors currently, but somewhat opposites: - GCC appears to evaluate weak constants _only_ in

[Bug middle-end/101836] __builtin_object_size(P->M, 1) where M is an array and the last member of a struct fails

2022-06-24 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #31

[Bug middle-end/101836] __builtin_object_size(P->M, 1) where M is an array and the last member of a struct fails

2022-07-06 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836 --- Comment #33 from James Y Knight --- (In reply to qinzhao from comment #32) > there is a Bugzilla that has been filed for GCC to request the same warning > for GCC: > https://gcc.gnu.org/bugzilla//show_bug.cgi?id=94428 > >

[Bug middle-end/101836] __builtin_object_size(P->M, 1) where M is an array and the last member of a struct fails

2022-07-06 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836 --- Comment #36 from James Y Knight --- (In reply to Kees Cook from comment #34) > > Great. Adding that flag, and eliminating the -fstrict-flex-arrays=3 option > > from this proposal would be good. > > Hmm? No, -fstrict-flex-arrays=3 is still

[Bug middle-end/101836] __builtin_object_size(P->M, 1) where M is an array and the last member of a struct fails

2022-07-06 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101836 --- Comment #37 from James Y Knight --- (In reply to qinzhao from comment #35) > I think that -Wstrict-flex-arrays will need to be cooperated with > -fstrict-flex-arrays=N, i.e, only when -fstrict-flex-arrays=N is presenting, >

[Bug c++/99858] Wrong throw-expression behaviour with reference to pointer

2022-06-10 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99858 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #3

[Bug target/55522] -funsafe-math-optimizations is unexpectedly harmful, especially w/ -shared

2022-09-06 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55522 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #12

[Bug target/98112] Add -f[no-]direct-access-external-data & drop HAVE_LD_PIE_COPYRELOC

2023-01-02 Thread foom at fuhm dot net via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98112 James Y Knight changed: What|Removed |Added CC||foom at fuhm dot net --- Comment #8