public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105960] Crash in 32-bit mode Date: Mon, 13 Jun 2022 20:00:49 +0000 [thread overview] Message-ID: <bug-105960-4-rujgOOtFj3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105960-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105960 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- > $COMPILE -c -o crash32.o crash32.c > $COMPILE -c -o expref.o expref.c > $CC -m32 -o liboink32.so -shared expref.o You didn't use -fPIC which is required if you are compiling a shared library.
next prev parent reply other threads:[~2022-06-13 20:00 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-13 19:54 [Bug c/105960] New: " terra at gnome dot org 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 [this message] 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-rujgOOtFj3@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).