[Bug c++/82309] Compiled binary received SIGSEGV when -g

2017-09-23 Thread sergio_nsk at yahoo dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82309 Sergey Markelov changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/82309] New: Compiled binary received SIGSEGV when -g

2017-09-23 Thread sergio_nsk at yahoo dot de
++ Assignee: unassigned at gcc dot gnu.org Reporter: sergio_nsk at yahoo dot de Target Milestone: --- Created attachment 42229 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42229=edit Source code I am learning expression templates. Compiled debug binary receives SIGS

[Bug c++/82309] Compiled binary received SIGSEGV when -g

2017-09-23 Thread sergio_nsk at yahoo dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82309 --- Comment #2 from Sergey Markelov --- Created attachment 42231 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42231=edit Assembler

[Bug c++/82309] Compiled binary received SIGSEGV when -g

2017-09-23 Thread sergio_nsk at yahoo dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82309 --- Comment #1 from Sergey Markelov --- Created attachment 42230 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42230=edit Preprocessed file

[Bug c++/82309] Compiled binary received SIGSEGV when -g

2017-09-24 Thread sergio_nsk at yahoo dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82309 --- Comment #6 from Sergey Markelov --- (In reply to Andrew Pinski from comment #5) > The temp variable goes out if scope is the result of v0 + v1. And not the > auto. IIRC -fsanitize=undefined will catch this. Yes, I agree, I understood it