[Bug web/114223] Utilize filtering for git://gcc.gnu.org/git/gcc.git

2024-03-03 Thread fche at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114223

Frank Ch. Eigler  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED
 CC||fche at redhat dot com

--- Comment #2 from Frank Ch. Eigler  ---
/etc/gitconfig now sports:

[uploadpack]
allowFilter = true

[Bug tree-optimization/113239] [13/14 regression] After 822a11a1e64, bogus -Warray-bounds warnings in std::vector

2024-01-22 Thread fche at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239

--- Comment #7 from Frank Ch. Eigler  ---
Wonder if this similar but different diagnostic is closely related:

https://kojipkgs.fedoraproject.org//work/tasks/6259/112176259/build.log

[...]
inlined from ‘mutatee::instrument_dynprobe_target(BPatch_object*,
dynprobe_target const&)’ at mutatee.cxx:444:22:
/usr/include/c++/14/bits/stl_algobase.h:438:30: error: ‘memmove’ writing
between 9 and 9223372036854775800 bytes into a region of size 0 overflows the
destination [-Werror=stringop-overflow=]
  438 | __builtin_memmove(__result, __first, sizeof(_Tp) * _Num);
  | ~^~~
In file included from
/usr/include/c++/14/x86_64-redhat-linux/bits/c++allocator.h:33,
 from /usr/include/c++/14/bits/allocator.h:46,
 from /usr/include/c++/14/string:43:
In member function ‘std::__new_allocator::allocate(unsigned
long, void const*)’,
[...]

where the c++ code in question is a straight

vector<> foo;
vector<> bar;
foo.insert(foo.end(), bar.begin(), bar.end());

[Bug debug/99654] Incorrect DW_AT_entry_pc values for inlined function

2021-03-29 Thread fche at redhat dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99654

--- Comment #4 from Frank Ch. Eigler  ---
A quick diff between the two -fverbose-asm dumps confirms that the generated
object code is identical with or without the -gno-as-locview-support, but the
DW_AT_entry_pc differs.