public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "terra at gnome dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/105960] New: Crash in 32-bit mode Date: Mon, 13 Jun 2022 19:54:25 +0000 [thread overview] Message-ID: <bug-105960-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105960 Bug ID: 105960 Summary: Crash in 32-bit mode Product: gcc Version: 12.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: terra at gnome dot org Target Milestone: --- Created attachment 53130 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53130&action=edit Source files and compile script The attached archive shows a crash when running 32-bit binaries compiled with gcc 12.1 I am preliminarily blaming the C compiler. 0. Unpack tar file 1. Edit "compile" to point at the desired compiler 2. ./compile 3. ./crash32 Expected: immediate return Observed: Segmentation fault (core dumped) (gdb) where #0 0xf7fc73d0 in *ABS*@plt () from /home/welinder/crash32/liboink32.so #1 0x0804841d in main () Observations (probably more "anecdote" than "data"): * Doesn't happen in 64-bit mode * Doesn't happen without optimization * The shared library appears to be a required part * The use target_clones appears to be a required part * This did not happen with gcc 11.1 # uname -a Linux xxxxxxxxxx 5.3.18-150300.59.63-default #1 SMP Tue Apr 5 12:47:31 UTC 2022 (d77db66) x86_64 x86_64 x86_64 GNU/Linux # /usr/local/products/gcc/12.1.0/bin/gcc --version gcc (GCC) 12.1.0 Copyright (C) 2022 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
next reply other threads:[~2022-06-13 19:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-13 19:54 terra at gnome dot org [this message] 2022-06-13 20:00 ` [Bug target/105960] " pinskia at gcc dot gnu.org 2022-06-13 20:00 ` pinskia at gcc dot gnu.org 2022-06-13 20:06 ` terra at gnome dot org 2022-06-13 20:08 ` terra at gnome dot org 2022-06-14 8:30 ` rguenth at gcc dot gnu.org 2022-06-14 8:31 ` [Bug target/105960] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-06-14 14:18 ` hjl.tools at gmail dot com 2022-06-14 15:02 ` hjl.tools at gmail dot com 2022-06-14 17:22 ` wwcsmail at gmail dot com 2022-06-20 15:26 ` cvs-commit at gcc dot gnu.org 2022-06-21 17:45 ` cvs-commit at gcc dot gnu.org 2022-07-15 9:00 ` marxin at gcc dot gnu.org 2022-07-15 18:07 ` hjl.tools at gmail dot com
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-105960-4@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).