public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/97129] [11 Regression] ICE in maybe_record_trace_start, at dwarf2cfi.c:2405 Date: Fri, 16 Oct 2020 14:48:22 +0000 [thread overview] Message-ID: <bug-97129-4-Uc61UR0LuM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97129-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97129 Uroš Bizjak <ubizjak at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #3 from Uroš Bizjak <ubizjak at gmail dot com> --- 'naked' This attribute allows the compiler to construct the requisite function declaration, while allowing the body of the function to be assembly code. The specified function will not have prologue/epilogue sequences generated by the compiler. Only basic 'asm' statements can safely be included in naked functions (*note Basic Asm::). While using extended 'asm' or a mixture of basic 'asm' and C code may appear to work, they cannot be depended upon to work reliably and are not supported.
prev parent reply other threads:[~2020-10-16 14:48 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 2:24 [Bug rtl-optimization/97129] New: " asolokha at gmx dot com 2020-09-21 6:56 ` [Bug rtl-optimization/97129] " rguenth at gcc dot gnu.org 2020-10-12 11:50 ` rguenth at gcc dot gnu.org 2020-10-16 14:24 ` marxin at gcc dot gnu.org 2020-10-16 14:48 ` ubizjak at gmail dot com [this message]
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-97129-4-Uc61UR0LuM@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).