public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luke-jr+gccbugs at utopios dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102993] -fcf-protection=full produces segfaulting code when targeting 32-bit x86 (i686)
Date: Fri, 29 Oct 2021 00:33:26 +0000 [thread overview]
Message-ID: <bug-102993-4-ST5ADodhLJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102993-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102993
Luke Dashjr <luke-jr+gccbugs at utopios dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|7.0 |9.3.0
--- Comment #2 from Luke Dashjr <luke-jr+gccbugs at utopios dot org> ---
# i686-w64-mingw32-g++ -v
Using built-in specs.
COLLECT_GCC=i686-w64-mingw32-g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-w64-mingw32/9.3-posix/lto-wrapper
Target: i686-w64-mingw32
Configured with: ../../src/configure --build=x86_64-linux-gnu --prefix=/usr
--includedir='/usr/include' --mandir='/usr/share/man'
--infodir='/usr/share/info' --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir='/usr/lib/x86_64-linux-gnu'
--libexecdir='/usr/lib/x86_64-linux-gnu' --disable-maintainer-mode
--disable-dependency-tracking --prefix=/usr --enable-shared --enable-static
--disable-multilib --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --libdir=/usr/lib --enable-libstdcxx-time=yes
--with-tune=generic --with-headers=/usr/i686-w64-mingw32/include
--enable-version-specific-runtime-libs --enable-fully-dynamic-string
--enable-libgomp --enable-languages=c,c++,fortran,objc,obj-c++,ada --enable-lto
--enable-threads=posix --program-suffix=-posix
--program-prefix=i686-w64-mingw32- --target=i686-w64-mingw32
--with-as=/usr/bin/i686-w64-mingw32-as --with-ld=/usr/bin/i686-w64-mingw32-ld
--enable-libatomic --enable-libstdcxx-filesystem-ts=yes
--enable-dependency-tracking
Thread model: posix
gcc version 9.3-posix 20200320 (GCC)
Apparently it's actually 9.3? (Was confused since the mingw-w64-i686-dev
package is 7.0.0-2, but g++-mingw-w64-i686 is indeed
9.3.0-7ubuntu1+22~exp1ubuntu4)
Not sure how to test newer GCC on Ubuntu, though I could try an entirely newer
version of Ubuntu if that would help.
next prev parent reply other threads:[~2021-10-29 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 23:56 [Bug other/102993] New: -mcf-protection=full " luke-jr+gccbugs at utopios dot org
2021-10-29 0:09 ` [Bug target/102993] -fcf-protection=full " pinskia at gcc dot gnu.org
2021-10-29 0:33 ` luke-jr+gccbugs at utopios dot org [this message]
2021-10-29 6:53 ` rguenth at gcc dot gnu.org
2021-10-29 7:05 ` ebotcazou at gcc dot gnu.org
2021-10-29 8:04 ` rguenth at gcc dot gnu.org
2021-10-29 8:08 ` ebotcazou at gcc dot gnu.org
2021-10-29 17:41 ` luke-jr+gccbugs at utopios dot org
2021-10-30 17:14 ` ebotcazou at gcc dot gnu.org
2022-12-27 7:11 ` nightstrike 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-102993-4-ST5ADodhLJ@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: link
Be 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).