public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98667] gcc generates endbr32 invalid opcode on -march=i486
Date: Thu, 14 Jan 2021 15:45:31 +0000	[thread overview]
Message-ID: <bug-98667-4-qs4l6kn0H8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98667-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98667

--- Comment #10 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Matthew Whitehead from comment #1)
> Here is the full set of compiler flags used.
> 
> readelf --string-dump='.GCC.command.line' /usr/lib/debug/$( which eix
> ).debug  
> 
> String dump of section '.GCC.command.line':
>   [     0]  -I .
>   [     5]  -I ..
>   [     b]  -D_GNU_SOURCE
>   [    19]  -D HAVE_CONFIG_H
>   [    2a]  -D SYSCONFDIR="/etc"
>   [    3f]  -D LOCALEDIR="/usr/share/locale"
>   [    60]  -D _FORTIFY_SOURCE=2
>   [    75]  various/drop_permissions.cc
>   [    91]  -march=i486
>   [    9d]  -auxbase-strip various/drop_permissions.o
>   [    c7]  -g
>   [    ca]  -ggdb
>   [    d0]  -O2
>   [    d4]  -fdata-sections
>   [    e4]  -ffunction-sections
>   [    f8]  -fcf-protection=full
>

Please remove -fcf-protection=full.

  parent reply	other threads:[~2021-01-14 15:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  1:24 [Bug c++/98667] New: " tedheadster at gmail dot com
2021-01-14  1:28 ` [Bug c++/98667] " tedheadster at gmail dot com
2021-01-14  7:28 ` [Bug target/98667] " pinskia at gcc dot gnu.org
2021-01-14 11:53 ` tedheadster at gmail dot com
2021-01-14 13:22 ` tedheadster at gmail dot com
2021-01-14 13:29 ` jakub at gcc dot gnu.org
2021-01-14 14:04 ` rguenth at gcc dot gnu.org
2021-01-14 14:07 ` hjl.tools at gmail dot com
2021-01-14 14:08 ` hjl.tools at gmail dot com
2021-01-14 15:43 ` cvs-commit at gcc dot gnu.org
2021-01-14 15:45 ` hjl.tools at gmail dot com [this message]
2021-01-15 13:26 ` tedheadster at gmail dot com
2021-04-27 13:12 ` hjl.tools at gmail dot com
2021-07-15 17:40 ` hjl.tools at gmail dot com
2021-10-21 15:22 ` marxin at gcc dot gnu.org
2021-10-21 15:55 ` hjl.tools at gmail dot com
2021-10-21 16:14 ` marxin at gcc dot gnu.org
2021-10-21 19:09 ` cvs-commit at gcc dot gnu.org
2021-10-21 19:10 ` cvs-commit at gcc dot gnu.org
2021-10-21 19:11 ` cvs-commit at gcc dot gnu.org
2021-10-21 19:14 ` cvs-commit 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-98667-4-qs4l6kn0H8@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).