[Bug c++/67056] Wrong code generated

2015-08-04 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

--- Comment #7 from Markus Trippelsdorf trippels at gcc dot gnu.org ---
Created attachment 36126
  -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36126action=edit
Somewhat reduced testcase


[Bug c++/67056] Wrong code generated

2015-08-04 Thread veg...@yahoo-inc.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

Vegard Sjonfjell veg...@yahoo-inc.com changed:

   What|Removed |Added

 CC||veg...@yahoo-inc.com

--- Comment #5 from Vegard Sjonfjell veg...@yahoo-inc.com ---
Created attachment 36122
  -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36122action=edit
Minimal failing example

We've tried to strip the code down to a minimal failing example. Compile with
-O3 -fPIC -std=c++11 (or std=c++14).


[Bug c++/67056] Wrong code generated

2015-08-04 Thread veg...@yahoo-inc.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

--- Comment #6 from Vegard Sjonfjell veg...@yahoo-inc.com ---
Created attachment 36123
  -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=36123action=edit
Preprocessed file

Also adding the preprocessed file.


[Bug c++/67056] Wrong code generated

2015-07-29 Thread bal...@yahoo-inc.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

--- Comment #4 from Henning Baldersheim bal...@yahoo-inc.com ---
Using the -fsanitize-undefined caused this error.
configretriever.cpp: info:  running test suite 'configretriever.cpp'
/home/y/include/c++/5.2.0/bits/unique_ptr.h:76:2: runtime error: execution
reached a __builtin_unreachable() call
make: *** [test] Error 1

While it works fine when not inlining the constructor.


[Bug c++/67056] Wrong code generated

2015-07-29 Thread trippels at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

Markus Trippelsdorf trippels at gcc dot gnu.org changed:

   What|Removed |Added

 CC||trippels at gcc dot gnu.org

--- Comment #2 from Markus Trippelsdorf trippels at gcc dot gnu.org ---
Also try to build your project with -fsanitize=undefined and see
if any issues pop up while running the unit tests.


[Bug c++/67056] Wrong code generated

2015-07-29 Thread bal...@yahoo-inc.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

--- Comment #3 from Henning Baldersheim bal...@yahoo-inc.com ---
valgrind does not complain about anything undefined, but will try the sanitize
option too.

Will also try to isolate it as much as possible.


[Bug c++/67056] Wrong code generated

2015-07-29 Thread ktkachov at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67056

--- Comment #1 from ktkachov at gcc dot gnu.org ---
There are some tips and instructions at:
https://gcc.gnu.org/bugs/

A reduced, preprocessed testcase would be ideal.