What did your debugger say? Was the segfault caused by dereferencing a pointer
returned by a failed dynamic_cast?
To my knowledge flto has never been working perfectly since g++ 4.8 on Windows:
multiple definitions, undefined references, pointer-to-function referring
garbage memory, valid
Hi,
I am the main developer of Win-builds.
NB 1: I slept 4 hours
NB 2: I'll be away from keyboard, maybe for 24 hours
On Fri, May 29, 2015, Prasanna V. Loganathar wrote:
Hi,
I had been using the builds as a part of MSYS2 for a while now, and I
believe this is the most robust and easiest
2015-05-29 13:36 GMT+02:00 Riot rain.back...@gmail.com:
I have to disagree. I use lto in large production builds with great
success. My use case is performance critical (games) and I build with
-Ofast as well as lto and other heavy optimisations without problems,
generating executable
I have to disagree. I use lto in large production builds with great
success. My use case is performance critical (games) and I build with
-Ofast as well as lto and other heavy optimisations without problems,
generating executable binaries of over a hundred megabytes in size when
stripped and
That's difficult to know, since the debugger seems to miss some information.
The current function where the crash occurs is unknown :?? in the level 1
stack view
For levels 2,3 and 4 I have the function name, but I have no access to the
location in the code.
Only level 5 of the stack is fully
On 05/28/2015 08:46 PM, Hotmail (ArbolOne) wrote:
Hi!
When using this the [[ noreturn ]] attribute like this: - void f [[
noreturn ]] (); - I get a warning that reads:
warning: 'noreturn' function does return
( http://www.stroustrup.com/C++11FAQ.html#attributes )
What can I do to remove this
Oh I can absolutely see why you might not want to enable it by default, but
in special cases where performance is worth the extra manual fuss of
working around its very occasional bugs, it's quite useful.
So I did a release build of our current primary project without LTO, and
compared it to our
Thank you, I did not understand the purpose of the attribute, but now it is
clear.
-Original Message-
From: Martin Sebor
Sent: Friday, May 29, 2015 5:21 PM
To: Hotmail (ArbolOne) ; gcc-help Mailing List ; MinGW-64 Mailinglist
Subject: Re: [[ noreturn ]]
On 05/29/2015 03:03 PM, Hotmail
This is the actual code where the test takes place:
void ascii_all [[ noreturn ]] () {
uint32_t ASCII_MAX = 255;
std::wstring a;
for (uint32_t i = 0; i = ASCII_MAX; i++) {
a = i;
size_t w1/*, w2*/;
if ( i 10 ) w1 = 3;
else w1 = 2;
wcout setw(
On 05/29/2015 03:03 PM, Hotmail (ArbolOne) wrote:
This is the actual code where the test takes place:
void ascii_all [[ noreturn ]] () {
uint32_t ASCII_MAX = 255;
std::wstring a;
for (uint32_t i = 0; i = ASCII_MAX; i++) {
a = i;
size_t w1/*, w2*/;
if (
10 matches
Mail list logo
