[Bug libgcc/69997] GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-03-03 Thread tcliuqiang at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997 Liu Qiang changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libgcc/69997] GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-03-02 Thread tcliuqiang at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997 --- Comment #5 from Liu Qiang --- Should I try to enable the MD_FALLBACK_FRAME_STATE_FOR for target specific fallback mechanism? in file src/gcc-5.3.0/libgcc/config/i386/linux-unwind.h, #ifndef inhibit_libc #define MD_FALLBACK_FRAME_STATE_FOR

[Bug libgcc/69997] GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-03-01 Thread tcliuqiang at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997 --- Comment #4 from Liu Qiang --- Hello everybody. I build the powerpc64 crosstoolchain with removing the 'gcc_assert(code==URC_NO_REASON)', and run the new system built by it. The program (python3 with thread exiting) terminated by SIGSEGV ins

[Bug libgcc/69997] GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-03-01 Thread tcliuqiang at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997 --- Comment #3 from Liu Qiang --- Latest info: uw_frmae_state_for return: 5 _URC_END_OF_STACK = 5, And I find that it is harmless to remove the gcc_assert(...). will it be the resolution? uw_init_context_1 (struct _Unwind_Context *context,

[Bug libgcc/69997] GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-02-28 Thread tcliuqiang at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997 --- Comment #2 from Liu Qiang --- yeah, i recommitted the page before the first committing done.

[Bug libgcc/69997] GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-02-28 Thread tcliuqiang at msn dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69997 Liu Qiang changed: What|Removed |Added Keywords||EH Severity|normal

[Bug libgcc/69998] New: GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-02-27 Thread tcliuqiang at msn dot com
Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: tcliuqiang at msn dot com Target Milestone: --- Hello GCC team. I build the cross toolchain for c,c++ myself (for multiple architectures like x86, arm, powerpc, mips). One thing

[Bug libgcc/69997] New: GCC5.3.0 _Unwind_ForcedUnwind Always Abort While pthread_exit

2016-02-27 Thread tcliuqiang at msn dot com
Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: tcliuqiang at msn dot com Target Milestone: --- Hello the GCC team. I build the cross toolchain for c,c++ myself (for multiple architectures like x86, arm, powerpc, mips). One thing

[Bug c/58730] New: arm-eabi-gcc generate error instructions for armv4t cpu

2013-10-14 Thread tcliuqiang at msn dot com
Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: tcliuqiang at msn dot com I build two versions of gcc: 4.7.3, and 4.8.1. the configure line listed as followed: mkdir -p build/gcc_arm; cd build/gcc_arm ../../src/gcc-4.8.1/configure --target=$target