public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/90378] [9/10 regression] -Os -flto miscompiles 454.calculix after r266385 on Arm Date: Wed, 11 Mar 2020 13:43:37 +0000 [thread overview] Message-ID: <bug-90378-4-OjjYsH8wDj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-90378-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90378 Christophe Lyon <clyon at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-03-11 CC| |clyon at gcc dot gnu.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #7 from Christophe Lyon <clyon at gcc dot gnu.org> --- I am able to reproduce the failure with the same commit mentioned by Maxim in comment #3. Using a more recent trunk (Feb 21, 2020) made the problem disappear. I'm using -Os -flto -mthumb, with a GCC bootstrapped on an armv7 machine (cortex-a15, NVidia jetson-tk1). Like Maxim said in comment #1, if I copy the binary and runtime libs (libgfortran, etc....) to an ARMv8 machine with AArch32 mode support, the execution is successful. The failure looks like this: ==================================== [...] increment 1 attempt 1 increment size= 5.000000e-02 sum of previous increments=0.000000e+00 ilin=0 iteration 1 Segmentation fault ==================================== Under gdb: Program received signal SIGSEGV, Segmentation fault. 0xb6deab58 in ?? () from /home/christophe.lyon/calculix.broken/lib/libc.so.6 (gdb) bt #0 0xb6deab58 in ?? () from /home/christophe.lyon/calculix.broken/lib/libc.so.6 #1 0xb6deb01e in ?? () from /home/christophe.lyon/calculix.broken/lib/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) When using valgrind (3.11.0), several errors are reported before reaching the point where the code normally crashes, but execution continues: ==================================== [...] increment 1 attempt 1 increment size= 5.000000e-02 sum of previous increments=0.000000e+00 ilin=0 iteration 1 largest residual force= 203.899659 no convergence iteration 2 ==================================== Most of the errors are "Invalid write of size 4" or "Use of uninitialised value of size 4" in bpabi.S lines 256-259, which correspond to macro expansion of push_for_divide and pop_for_divide in aeabi_uldivmod. The errors are about reading/writing in the stack. When using valgrind (3.13.0) on ARMv8 hardware, it does not report any error, so I'm puzzled: was it a bug in valgrind-3.11.0, or are some glibc ifuncs changing the behaviour? Anyway, I still don't know where the program crashes on ARMv7 hardware.
next parent reply other threads:[~2020-03-11 13:43 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-90378-4@http.gcc.gnu.org/bugzilla/> 2020-03-11 13:43 ` clyon at gcc dot gnu.org [this message] 2020-03-12 10:08 ` clyon at gcc dot gnu.org 2020-03-12 11:58 ` jakub at gcc dot gnu.org 2020-03-13 14:06 ` clyon at gcc dot gnu.org 2021-06-01 8:14 ` [Bug rtl-optimization/90378] [9/10/11/12 " rguenth at gcc dot gnu.org 2021-06-01 10:02 ` mkuvyrkov at gcc dot gnu.org 2021-10-01 16:03 ` mkuvyrkov 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-90378-4-OjjYsH8wDj@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).