[Bug libstdc++/109703] New: __builtin_unreachable() reached

2023-05-02 Thread christian.morales.vega at gmail dot com via Gcc-bugs
++ Assignee: unassigned at gcc dot gnu.org Reporter: christian.morales.vega at gmail dot com Target Milestone: --- This (https://github.com/gcc-mirror/gcc/commit/bf78b43873b0b7e8f9a430df38749b8b61f9c9b8#diff-c8a656ef205ec6452ef0bed111a387dc9e7eb2404fb3222a48f9f93b2460bd55R278

[Bug libstdc++/105616] Using regex_replace throws "maybe-uninitialized" warnings

2022-07-11 Thread christian.morales.vega at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105616 --- Comment #2 from Cristian Morales Vega --- I don't think so. Supposedly it was fixed 2 months ago in trunk (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105562#c14). But in https://godbolt.org/z/8a979Gha8 the warnings are still present (even

[Bug libstdc++/105671] [11/12/13 Regression] Unexplained "undefined reference" error

2022-05-27 Thread christian.morales.vega at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105671 --- Comment #4 from Cristian Morales Vega --- I can confirm adding "__attribute__((always_inline))" in _M_high_mark() solves the issue.

[Bug c++/105671] Unexplained "undefined reference" error

2022-05-20 Thread christian.morales.vega at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105671 --- Comment #1 from Cristian Morales Vega --- It's in the full verbose build log, but failed to include it here. These are the contents of the files: $ cat user-config.jam using gcc : : g++ : "-flto" ; $ cat test.cpp #include #include

[Bug c++/105671] New: Unexplained "undefined reference" error

2022-05-20 Thread christian.morales.vega at gmail dot com via Gcc-bugs
mponent: c++ Assignee: unassigned at gcc dot gnu.org Reporter: christian.morales.vega at gmail dot com Target Milestone: --- Created attachment 53005 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53005=edit Full verbose build log I have found a strange issue in my

[Bug libstdc++/105616] New: Using regex_replace throws "maybe-uninitialized" warnings

2022-05-16 Thread christian.morales.vega at gmail dot com via Gcc-bugs
ty: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: christian.morales.vega at gmail dot com Target Milestone: --- As can be seen in https://godbolt.org/z/qK976bqzf Building #include #include #include

[Bug c++/93490] -Wsuggest-attribute=const suggests const attribute for non-static member function

2020-01-29 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93490 Cristian Morales Vega changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c++/93490] -Wsuggest-attribute=const suggests const attribute for non-static member function

2020-01-29 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93490 --- Comment #7 from Cristian Morales Vega --- Oh, it isn't a bug because it's returning a reference and even if the value of member_ changes the reference (i.e. pointer) will always be the same?

[Bug c++/93490] -Wsuggest-attribute=const suggests const attribute for non-static member function

2020-01-29 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93490 --- Comment #6 from Cristian Morales Vega --- Yes, -- struct Class1 { int member_; }; int (Class1 *a) { return a->member_; } -- also generates the warning. This is a bug, right? I'm basing this issue on

[Bug c++/93490] -Wsuggest-attribute=const suggests const attribute for non-static member function

2020-01-29 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93490 --- Comment #3 from Cristian Morales Vega --- This seems to show the issue: https://godbolt.org/z/-VRgtF class Class1 { public: auto member() -> int& #ifdef INLINE { return member_; } #else ; #endif private: int member_; };

[Bug c++/93490] -Wsuggest-attribute=const suggests const attribute for non-static member function

2020-01-29 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93490 --- Comment #1 from Cristian Morales Vega --- The warning is not there when using ubsan/asan or tsan.

[Bug c++/93490] New: -Wsuggest-attribute=const suggests const attribute for non-static member function

2020-01-29 Thread christian.morales.vega at gmail dot com
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: christian.morales.vega at gmail dot com Target Milestone: --- I can't share the code triggering it. But gcc 9.2.1 from Fedora 31 is saying "function might be cand

[Bug gcov-profile/89961] When "--intermediate-format" is used "--preserve-paths"/"--hash-filenames" is ignored

2019-04-05 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961 --- Comment #5 from Cristian Morales Vega --- OK, trying to catch you here, from my gcc-8.3.1. So with gcc 9 "--intermediate-format" is gone and we now have "--json-format" (keeping the "-i" version)? The "--intermediate-format" documentation

[Bug gcov-profile/89961] When "--intermediate-format" is used "--preserve-paths"/"--hash-filenames" is ignored

2019-04-04 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89961 --- Comment #3 from Cristian Morales Vega --- I have just took a look inside one of the intermediate format .gcov files and didn't see any "current_working_directory". There is a full path "file" variable though. Not sure if that's what you

[Bug gcov-profile/89961] New: When "--intermediate-format" is used "--preserve-paths"/"--hash-filenames" is ignored

2019-04-04 Thread christian.morales.vega at gmail dot com
Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: christian.morales.vega at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Fedora 29, gcc-8

[Bug gcov-profile/89959] gcov: "--long-file-names" is ignored when used in combination with "--hash-filenames"

2019-04-04 Thread christian.morales.vega at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89959 --- Comment #1 from Cristian Morales Vega --- At the end of my previous comment .gcov should actually be ##.gcov

[Bug gcov-profile/89959] New: gcov: "--long-file-names" is ignored when used in combination with "--hash-filenames"

2019-04-04 Thread christian.morales.vega at gmail dot com
Status: UNCONFIRMED Severity: normal Priority: P3 Component: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: christian.morales.vega at gmail dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Fedora 29, gcc-8.3.1-2.fc2