public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/102955] New: assembler errors when bootstrapping with #pragma optimize "0"
Date: Tue, 26 Oct 2021 17:36:04 +0000 [thread overview]
Message-ID: <bug-102955-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102955
Bug ID: 102955
Summary: assembler errors when bootstrapping with #pragma
optimize "0"
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
This is to make a record of a problem I recently ran into with GCC 12 and that
apparently others have as well. As discussed here:
https://gcc.gnu.org/pipermail/gcc/2021-October/237616.html
Putting #pragma GCC optimize "0" at the top of gimplify.c to debug something in
a bootstrapped compiler causes the file to fail to assemble with a stage 2 GCC
due to many assembler errors like this:
/tmp/ccL9zcXD.s: Assembler messages:
/tmp/ccL9zcXD.s:9: Error: CFI instruction used without previous
.cfi_startproc
The top of gimplify.s is below (this is with no other code changes to any files
except the #pragma).
.file "gimplify.c"
.text
.local _ZZ20gimplify_va_arg_exprPP9tree_nodePP6gimpleS4_E9gave_help
.comm
_ZZ20gimplify_va_arg_exprPP9tree_nodePP6gimpleS4_E9gave_help,1,1
.p2align 4
.type _ZL19handled_component_pPK9tree_node, @function
_ZL19handled_component_pPK9tree_node:
pushq %rbp
.cfi_def_cfa_offset 16
.cfi_offset 6, -16
movq %rsp, %rbp
.cfi_def_cfa_register 6
movq %rdi, -8(%rbp)
movq -8(%rbp), %rax
movzwl (%rax), %eax
movzwl %ax, %eax
subl $47, %eax
cmpl $6, %eax
ja .L2
movl $1, %eax
jmp .L3
.L2:
movl $0, %eax
.L3:
popq %rbp
.cfi_def_cfa 7, 8
ret
next reply other threads:[~2021-10-26 17:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 17:36 msebor at gcc dot gnu.org [this message]
2021-10-26 22:28 ` [Bug middle-end/102955] " pinskia at gcc dot gnu.org
2021-10-26 22:29 ` [Bug debug/102955] " pinskia at gcc dot gnu.org
2021-10-26 22:32 ` pinskia at gcc dot gnu.org
2021-10-26 22:35 ` pinskia at gcc dot gnu.org
2021-10-26 22:42 ` pinskia at gcc dot gnu.org
2021-10-26 23:05 ` pinskia at gcc dot gnu.org
2021-10-26 23:07 ` [Bug debug/102955] [12 Regression] ICE with #pragma optimize "0" and -g -gtoggle pinskia at gcc dot gnu.org
2021-10-26 23:12 ` pinskia at gcc dot gnu.org
2021-10-28 10:02 ` acoplan at gcc dot gnu.org
2021-10-28 22:35 ` [Bug debug/102955] [12 Regression] ICE with #pragma optimize "0" or attribute optimize " pinskia at gcc dot gnu.org
2021-11-01 3:59 ` marxin at gcc dot gnu.org
2021-11-05 12:01 ` cvs-commit at gcc dot gnu.org
2021-11-05 12:02 ` marxin 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-102955-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: 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).