public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thiago.bauermann at linaro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110796] builtin_iseqsig fails some tests in armv8l-linux-gnueabihf Date: Tue, 25 Jul 2023 16:44:51 +0000 [thread overview] Message-ID: <bug-110796-4-kypIM5sJok@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110796-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110796 --- Comment #4 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> --- Thanks for looking into this. (In reply to Francois-Xavier Coudert from comment #3) > Do the failure only occur at -Os? Only at -Os. The FAILs I mentioned in the bug report are the only ones that occur. > Does it pass at -O0, -O1, -O2? Yes. > And could you possibly run builtin-iseqsig-1.c under gdb and obtain a > backtrace? Here it is: thiago.bauermann@tcwg-jade-03-dev:~/tmp$ /home/thiago.bauermann/.cache/builds/gcc-native-aarch32/gcc/xgcc -B/home/thiago.bauermann/.cache/builds/gcc-native-aarch32/gcc/ /home/thiago.bauermann/src/gcc/gcc/testsuite/gcc.dg/torture/builtin-iseqsig-1.c -fdiagnostics-plain-output -Os -fsignaling-nans -ggdb3 -lm -o ./builtin-iseqsig-1.exe thiago.bauermann@tcwg-jade-03-dev:~/tmp$ gdb builtin-iseqsig-1.exe Reading symbols from builtin-iseqsig-1.exe... (gdb) r Starting program: /home/thiago.bauermann/tmp/builtin-iseqsig-1.exe [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1". Program received signal SIGABRT, Aborted. __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 47 ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S: No such file or directory. (gdb) bt #0 __libc_do_syscall () at ../sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:47 #1 0xf7e8d2ca in __pthread_kill_implementation (threadid=4160625664, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:43 #2 0xf7e8d30c in __pthread_kill_internal (signo=6, threadid=<optimized out>) at pthread_kill.c:78 #3 0xf7e5c840 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0xf7e4d5e4 in __GI_abort () at abort.c:79 #5 0x00010426 in main () at /home/thiago.bauermann/src/gcc/gcc/testsuite/gcc.dg/torture/builtin-iseqsig-1.c:30 (gdb) frame 5 #5 0x00010426 in main () at /home/thiago.bauermann/src/gcc/gcc/testsuite/gcc.dg/torture/builtin-iseqsig-1.c:30 30 if (fetestexcept (FE_INVALID)) __builtin_abort (); (gdb)
next prev parent reply other threads:[~2023-07-25 16:44 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-24 22:36 [Bug middle-end/110796] New: " thiago.bauermann at linaro dot org 2023-07-24 22:39 ` [Bug target/110796] " pinskia at gcc dot gnu.org 2023-07-24 22:50 ` thiago.bauermann at linaro dot org 2023-07-25 15:13 ` fxcoudert at gcc dot gnu.org 2023-07-25 16:44 ` thiago.bauermann at linaro dot org [this message] 2023-07-25 16:50 ` fxcoudert at gcc dot gnu.org 2023-07-25 17:13 ` rearnsha at gcc dot gnu.org 2023-07-25 17:14 ` thiago.bauermann at linaro dot org 2023-07-25 17:17 ` fxcoudert at gcc dot gnu.org 2023-07-25 17:18 ` rearnsha at gcc dot gnu.org 2023-07-25 17:48 ` thiago.bauermann at linaro dot org 2023-07-26 16:58 ` rearnsha at gcc dot gnu.org 2023-08-02 10:38 ` rearnsha at gcc dot gnu.org 2024-01-05 14:49 ` xry111 at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-110796-4-kypIM5sJok@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).