public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "worx at pouf dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/99703] gcc-10.2.0 with Via C3 Eden: configure: error: Intel CET must be enabled on Intel CET enabled host
Date: Tue, 23 Mar 2021 21:46:47 +0000 [thread overview]
Message-ID: <bug-99703-4-NYEfetr6Ev@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99703-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99703
--- Comment #24 from Worx <worx at pouf dot org> ---
worx@c3eden ~ $ gdb ./sample.bin
GNU gdb (Gentoo 10.1 vanilla) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "i586-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://bugs.gentoo.org/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./sample.bin...
(No debugging symbols found in ./sample.bin)
(gdb) run
Starting program: /home/worx/sample.bin
Program received signal SIGILL, Illegal instruction.
0x0804f547 in ?? ()
(gdb)
next prev parent reply other threads:[~2021-03-23 21:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-21 23:57 [Bug libgcc/99703] New: " worx at pouf dot org
2021-03-22 0:00 ` [Bug libgcc/99703] " worx at pouf dot org
2021-03-22 8:20 ` [Bug target/99703] " marxin at gcc dot gnu.org
2021-03-22 9:18 ` rguenth at gcc dot gnu.org
2021-03-22 12:47 ` worx at pouf dot org
2021-03-22 12:47 ` worx at pouf dot org
2021-03-22 12:48 ` worx at pouf dot org
2021-03-22 12:52 ` rguenth at gcc dot gnu.org
2021-03-22 12:52 ` marxin at gcc dot gnu.org
2021-03-22 12:59 ` jakub at gcc dot gnu.org
2021-03-22 13:10 ` worx at pouf dot org
2021-03-22 18:34 ` hjl.tools at gmail dot com
2021-03-22 19:10 ` slyfox at gcc dot gnu.org
2021-03-22 19:20 ` slyfox at gcc dot gnu.org
2021-03-22 19:27 ` slyfox at gcc dot gnu.org
2021-03-22 19:27 ` slyfox at gcc dot gnu.org
2021-03-22 19:53 ` worx at pouf dot org
2021-03-22 20:25 ` hjl.tools at gmail dot com
2021-03-23 0:52 ` worx at pouf dot org
2021-03-23 15:40 ` worx at pouf dot org
2021-03-23 15:44 ` hjl.tools at gmail dot com
2021-03-23 15:54 ` worx at pouf dot org
2021-03-23 16:00 ` hjl.tools at gmail dot com
2021-03-23 19:46 ` hjl.tools at gmail dot com
2021-03-23 21:46 ` worx at pouf dot org [this message]
2021-03-23 21:53 ` hjl.tools at gmail dot com
2021-03-23 21:57 ` worx at pouf dot org
2021-03-23 21:59 ` worx at pouf dot org
2021-03-23 22:09 ` hjl.tools at gmail dot com
2021-03-23 22:12 ` jakub at gcc dot gnu.org
2021-03-23 22:53 ` worx at pouf dot org
2021-03-23 23:06 ` worx at pouf dot org
2021-03-25 0:34 ` worx at pouf dot org
2021-03-26 1:16 ` worx at pouf dot org
2021-05-03 12:01 ` cvs-commit at gcc dot gnu.org
2021-05-03 12:01 ` cvs-commit at gcc dot gnu.org
2021-05-03 12:45 ` 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-99703-4-NYEfetr6Ev@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).