[Bug c/64687] New: powerpc: GCC 5.0 (trunk@219851) build failure for powerpc with hardware decimal floating point disabled

2015-01-20 Thread azanella at linux dot vnet.ibm.com
: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: azanella at linux dot vnet.ibm.com Created attachment 34499 -- https://gcc.gnu.org/bugzilla/attachment.cgi?id=34499action=edit Testcase to trigger

[Bug target/64687] powerpc: GCC 5.0 (trunk@219851) build failure for powerpc with hardware decimal floating point disabled

2015-01-20 Thread azanella at linux dot vnet.ibm.com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64687 --- Comment #3 from Adhemerval Zanella azanella at linux dot vnet.ibm.com --- Yes, my GCC build have -mcpu=power7 -mtune=power8 option as configure option.

[Bug target/57363] IBM long double: adding NaN and number raises inexact exception

2013-07-03 Thread azanella at linux dot vnet.ibm.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57363 --- Comment #2 from Adhemerval Zanella azanella at linux dot vnet.ibm.com --- You are correct and I meant in my first comment QNaN for the NaN work. And I believe the patch is still correct: for IBM long double SNaN will be represented by first

[Bug target/57363] New: IBM long double: adding NaN and number raises inexact exception

2013-05-21 Thread azanella at linux dot vnet.ibm.com
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: azanella at linux dot vnet.ibm.com For IBM long double, adding a normal number to a NaN raises an inexact exception. Adding any number to NaN should not raise any exception

[Bug libstdc++/54393] std::getline is almost 10x slower when working on a vstring versus std::string

2012-08-28 Thread azanella at linux dot vnet.ibm.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54393 --- Comment #2 from Adhemerval Zanella azanella at linux dot vnet.ibm.com 2012-08-28 18:44:44 UTC --- Created attachment 28094 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=28094 __gnu_ext::__vstring getline optimization

[Bug libstdc++/54393] std::getline is almost 10x slower when working on a vstring versus std::string

2012-08-28 Thread azanella at linux dot vnet.ibm.com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54393 --- Comment #3 from Adhemerval Zanella azanella at linux dot vnet.ibm.com 2012-08-28 18:49:42 UTC --- The default algorithm used on both std::string and __gnu_cxx::__vstring appends data char by char. However, std::string also provides