[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2024-12-23 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 --- Comment #21 from Yury Gribov --- (In reply to Gabriel Ravier from comment #20) > I hope you would agree memory corruption is bad - and that's what will > happen a lot of the time instead of a simple crash. Ok, got it. So basically memory co

[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2024-12-23 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 --- Comment #19 from Yury Gribov --- (In reply to Jonathan Wakely from comment #17) > (In reply to Yury Gribov from comment #10) > > As a compiler user I would actually love my STL to crash fast on invalid > > comparators rather than produce unp

[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2024-12-21 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 --- Comment #16 from Yury Gribov --- (In reply to Xi Ruoyao from comment #15) > (In reply to Yury Gribov from comment #14) > > (In reply to Xi Ruoyao from comment #12) > > > Also note even > > > > > > bool cmp(Element a, Element b) { return fal

[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2024-12-21 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 --- Comment #14 from Yury Gribov --- (In reply to Xi Ruoyao from comment #12) > Also note even > > bool cmp(Element a, Element b) { return false; } > > is a *valid* comparator, per the standard. Hm, doesn't it violate the asymmetry axiom (cmp

[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2024-12-21 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 --- Comment #13 from Yury Gribov --- (In reply to Xi Ruoyao from comment #11) > (In reply to Yury Gribov from comment #10) > > As a compiler user I would actually love my STL to crash fast on invalid > > comparators rather than produce unpredict

[Bug libstdc++/113159] More robust std::sort for silly comparator functions

2024-12-21 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113159 Yury Gribov changed: What|Removed |Added CC||ygribov at gcc dot gnu.org --- Comment #1

[Bug sanitizer/106558] ASan failed to detect a global-buffer-overflow

2022-09-01 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106558 Yury Gribov changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|unassigned at

[Bug sanitizer/106558] ASan failed to detect a global-buffer-overflow

2022-09-01 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106558 Yury Gribov changed: What|Removed |Added Attachment #53458|0 |1 is obsolete|

[Bug sanitizer/106558] ASan failed to detect a global-buffer-overflow

2022-08-15 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106558 --- Comment #10 from Yury Gribov --- Created attachment 53458 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53458&action=edit Very draft patch (In reply to Jakub Jelinek from comment #7) > Perhaps either a quick check that for base ptrs

[Bug gcov-profile/47618] Collecting multiple profiles and using all for PGO

2022-01-06 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47618 Yury Gribov changed: What|Removed |Added CC||ygribov at gcc dot gnu.org --- Comment #29

[Bug libgomp/103276] [openacc] Trying to map already mapped data

2021-11-17 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103276 --- Comment #5 from Yury Gribov --- Created attachment 51823 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51823&action=edit Runnable reprocase I've attached another reprocase which reproduces the error at runtime (but let me reiterate t

[Bug libgomp/103276] [openacc] Trying to map already mapped data

2021-11-17 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103276 --- Comment #4 from Yury Gribov --- (In reply to Andrew Pinski from comment #3) > No the gimple is wrong. &var is taking the address of the argument. It > should just be var here if you what the reference points to rather than the > address of

[Bug libgomp/103276] [openacc] Trying to map already mapped data

2021-11-16 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103276 Yury Gribov changed: What|Removed |Added CC||ygribov at gcc dot gnu.org --- Comment #2

[Bug middle-end/102310] New: ICE in visit_ref_for_mod_analysis with OpenACC

2021-09-13 Thread ygribov at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102310 Bug ID: 102310 Summary: ICE in visit_ref_for_mod_analysis with OpenACC Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: m