[Bug c++/86370] try/catch exception in thread cause segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86370 Airbak changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/86370] New: try/catch exception in thread cause segmentation fault

Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: airbak.li at huawei dot com Target Milestone: --- 1. Code: #include #include #include #include void* func(void *arg) { try { int error = *(int *)arg; printf("thread error start:\n"); throw error; prin

[Bug c/78181] unrecognized option -mcpu=cortex-a73

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78181 Airbak changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|INVALID

[Bug c/78181] New: unrecognized option -mcpu=cortex-a73

Assignee: unassigned at gcc dot gnu.org Reporter: airbak.li at huawei dot com Target Milestone: --- When I build a cross-toolchain with gcc 6.2. When I used -mcpu=cortex-a73, it failed. When I used -mtune=cortex-a73, is OK. ljhui@key:~/toolchain/git/build-toolchain/gcc-uclibc$ /home

[Bug middle-end/64012] GCC-4.9.2 option -fcaller-saves in -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64012 Airbak changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|INVALID

[Bug middle-end/64012] GCC-4.9.2 option -fcaller-saves in -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64012 --- Comment #5 from Airbak --- I'm sorry for my mistake. GCC-4.8.3 also have this phenomenon. GCC 4.4.1 is OK.

[Bug middle-end/64012] GCC-4.9.2 option -fcaller-saves in -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64012 --- Comment #4 from Airbak --- When I build toolchain with GNU , the problem also exist. -- lijianhui@key:~/hi3535/Hi3535_SDK_V2.0.3.1/osdrv/kernel/linux-3.4.y$ arm-unknown-linux-gnueabi-gcc -v Using built-in specs. COLLECT_GCC=a

[Bug middle-end/64012] GCC-4.9.2 option -fcaller-saves in -O2

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64012 --- Comment #2 from Airbak --- lijianhui@key:~$ arm-unknown-linux-gnueabi-gcc -v Using built-in specs. COLLECT_GCC=arm-unknown-linux-gnueabi-gcc COLLECT_LTO_WRAPPER=/home/os/lijianhui/linaro/new-crosstool-ng/install-2-multilib/bin/../libexec/gcc/

[Bug c/64012] New: GCC-4.9.2 option -fcaller-saves in -O2

Assignee: unassigned at gcc dot gnu.org Reporter: airbak.li at huawei dot com A cross toolchain build by GCC-4.9.2, when I use this toolchain to compile kernel-3.4.35 with option -O2, it always crash when system power up. (CPU : armv-7 cortex-a9) ---Crash log

[Bug c/63803] When GCC 4.9.2 compile with option -O2, the target is error.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63803 Airbak changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #7 from Airbak --- Thank yo

[Bug c/63803] When GCC 4.9.2 compile with option -O2, the target is error.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63803 --- Comment #3 from Airbak --- Thank you for your reply! "-fisolate-erroneous-paths-dereference" is a new option in GCC-4.9.x. When I use GCC-4.8.x, it is OK and will not have this problem. More and more people are switching GCC4.8 to GCC4.9, I t

[Bug c/63803] New: When GCC 4.9.2 compile with option -O2, the target is error.

Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: airbak.li at huawei dot com The option -fisolate-erroneous-paths-dereference in -O2 causes it. 1.file b.c: int main() { //volatile unsigned int //unsigned int orgin = *((int *)0); //ok