http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54393
--- Comment #2 from Adhemerval Zanella
2012-08-28 18:44:44 UTC ---
Created attachment 28094
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=28094
__gnu_ext::__vstring getline optimization
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54393
--- Comment #3 from Adhemerval Zanella
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 an template
specialization for both char and
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. The
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57363
--- Comment #2 from Adhemerval Zanella ---
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 double being the NaN (the second doub
: 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=34499&action=edit
Testcase to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64687
--- Comment #3 from Adhemerval Zanella ---
Yes, my GCC build have -mcpu=power7 -mtune=power8 option as configure option.