> So, concluding, the following isn't correct?
>
> ,
> | #
> | #If SWISH++ doesn't work correctly with optimization on, but it
> | #works just fine with it off, then there is a bug in your
> | #compiler's optimizer.
> `
No. Something like
# If SWISH++ doesn't work
> "Martin" == Martin v Loewis <[EMAIL PROTECTED]> writes:
Thanks for the fast reply, Martin
[...]
>> Is the trial and error method the usual approach ? ;-)
Martin> No. Instead, one needs to clearly identify the problem. If
Martin> it is a compiler bug, it would fall into the c
> What are the known issues with those compilers?
The list is long, see
http://gcc.gnu.org/cgi-bin/gnatsweb.pl
> Is the trial and error method the usual approach ? ;-)
No. Instead, one needs to clearly identify the problem. If it is a
compiler bug, it would fall into the class "generates bad co
I've taken over recently the swish++ package, so far so good.
After two weeks I got some bug reports of segfaults that I wasn't able
to reproduce first. Now I can reproduce them with another command.
Ok here are the results of my fiddling around with different
compilers.
i386:
2.95.4 : without
4 matches
Mail list logo
