https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98209
--- Comment #8 from jamesgua at ca dot ibm.com ---
one more function found the same issue:
memcpy
I guess more functions in libc might have same issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98209
--- Comment #2 from jamesgua at ca dot ibm.com ---
Created attachment 49709
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49709&action=edit
preprocessed src file gcc -E
Assignee: unassigned at gcc dot gnu.org
Reporter: jamesgua at ca dot ibm.com
Target Milestone: ---
Testing file:
#include
int main(int argc, char** argv) __attribute__ ((__target__ ("no-sse,no-mmx")));
int main(int argc, char** argv)
{
printf("hello!\n"
++
Assignee: unassigned at gcc dot gnu.org
Reporter: jamesgua at ca dot ibm.com
Target Milestone: ---
With g++ 8.3.1 version
GNU C++14 (GCC) version 8.3.1 20190507 (Red Hat 8.3.1-4) (x86_64-redhat-linux)
compiled by GNU C version 8.3.1 20190507 (Red Hat 8.3.1-4), GMP version
y: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: jamesgua at ca dot ibm.com
Target Milestone: ---
In DWARF 4 spec DW_ATE_UTF is value 0x10 or 16, but objdump can't map that
value to UTF, instead, print "unknown type":
e.g.
char16_t utf16
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61574
--- Comment #4 from jamesgua at ca dot ibm.com ---
Found the same issue with G++ 4.6.1 on zLinux.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61574
--- Comment #2 from jamesgua at ca dot ibm.com ---
(In reply to Andrew Pinski from comment #1)
> This is deconstructors.
I mean why we have those line numbers "17 9 17 9 17", debugger follow the line
number information and user
++
Assignee: unassigned at gcc dot gnu.org
Reporter: jamesgua at ca dot ibm.com
#include
#include
using namespace std;
int main(int argc, char** argv)
{
string str1 = "Hello";
string str2;
str2 = str1;
cout << "str2: " << str2 &
