public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112334] ICE in gen_untyped_return arm.md:9197 while compiling harden-cfr-bret.c
Date: Thu, 02 Nov 2023 13:03:51 +0000	[thread overview]
Message-ID: <bug-112334-4-epVwQl4STq@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112334-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
This might be a side issue, but:

@defbuiltin{{void} __builtin_return (void *@var{result})}
This built-in function returns the value described by @var{result} from
the containing function.  You should specify, for @var{result}, a value
returned by @code{__builtin_apply}.

So I'm not sure it's legal to pass &i to __builtin_return().

  reply	other threads:[~2023-11-02 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 13:18 [Bug target/112334] New: " fkastl at suse dot cz
2023-11-02 13:03 ` rearnsha at gcc dot gnu.org [this message]
2023-12-01 17:38 ` [Bug target/112334] " cvs-commit at gcc dot gnu.org
2023-12-06 21:47 ` aoliva at gcc dot gnu.org
2023-12-12  4:16 ` cvs-commit at gcc dot gnu.org
2023-12-12  4:46 ` aoliva 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-112334-4-epVwQl4STq@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).