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 c/105970] ICE in ix86_function_arg, at config/i386/i386.cc:3351 Date: Tue, 14 Jun 2022 15:12:30 +0000 [thread overview] Message-ID: <bug-105970-4-3EygTrrgr2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105970-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105970 --- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Uroš Bizjak from comment #1) > Probably something like: > > diff --git a/gcc/config/i386/i386.cc b/gcc/config/i386/i386.cc > index 3d189e124e4..f158cc3aaea 100644 > --- a/gcc/config/i386/i386.cc > +++ b/gcc/config/i386/i386.cc > @@ -3348,7 +3348,7 @@ ix86_function_arg (cumulative_args_t cum_v, const > function_arg_info &arg) > if (POINTER_TYPE_P (arg.type)) > { > /* This is the pointer argument. */ > - gcc_assert (TYPE_MODE (arg.type) == Pmode); > + gcc_assert (TYPE_MODE (arg.type) == ptr_mode); This looks reasonable since pointer mode should be ptr_mode. > /* It is at -WORD(AP) in the current frame in interrupt and > exception handlers. */ > reg = plus_constant (Pmode, arg_pointer_rtx, -UNITS_PER_WORD); > > Pointer mode and Pmode can be distinct for x32 target. However, I have no > idea what goes into interrupt frame for x32. Let's ask HJ.
next prev parent reply other threads:[~2022-06-14 15:12 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-14 10:25 [Bug c/105970] New: " gscfq@t-online.de 2022-06-14 11:55 ` [Bug c/105970] " ubizjak at gmail dot com 2022-06-14 15:12 ` hjl.tools at gmail dot com [this message] 2022-06-17 15:02 ` cvs-commit at gcc dot gnu.org 2022-06-20 18:33 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:06 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:32 ` cvs-commit at gcc dot gnu.org 2022-06-20 20:36 ` [Bug target/105970] " ubizjak 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-105970-4-3EygTrrgr2@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).