public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62133] internal compiler error:in classify_argument, at config/i386/i386.c:6240 when using #pragma GCC target ("arch=core-avx2")
Date: Wed, 19 Oct 2022 14:34:33 +0000 [thread overview]
Message-ID: <bug-62133-4-FINOjPVUK9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62133-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62133
--- Comment #3 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Zdenek Sojka from comment #2)
> Another testcase, for C code:
> $ cat testcase.c
> __bf16 __attribute__((__vector_size__(8))) foo(void) {}
> $ x86_64-pc-linux-gnu-gcc testcase.c
> testcase.c: In function 'foo':
> testcase.c:1:1: internal compiler error: in classify_argument, at
> config/i386/i386.cc:2523
> 1 | __bf16 __attribute__((__vector_size__(8))) foo(void) {}
> | ^~~~~~
> 0x8437a7 classify_argument
> /repo/gcc-trunk/gcc/config/i386/i386.cc:2523
> 0x1788e56 classify_argument
> /repo/gcc-trunk/gcc/config/i386/i386.cc:2543
> 0x1788f28 examine_argument
> /repo/gcc-trunk/gcc/config/i386/i386.cc:2580
> 0x17898af ix86_return_in_memory
> /repo/gcc-trunk/gcc/config/i386/i386.cc:4265
> 0x1044e71 aggregate_value_p(tree_node const*, tree_node const*)
> /repo/gcc-trunk/gcc/function.cc:2119
> 0x1049981 allocate_struct_function(tree_node*, bool)
> /repo/gcc-trunk/gcc/function.cc:4848
> 0xd596a4 store_parm_decls()
> /repo/gcc-trunk/gcc/c/c-decl.cc:10434
> 0xdbdced c_parser_declaration_or_fndef
> /repo/gcc-trunk/gcc/c/c-parser.cc:2612
> 0xdc5eb3 c_parser_external_declaration
> /repo/gcc-trunk/gcc/c/c-parser.cc:1833
> 0xdc68d3 c_parser_translation_unit
> /repo/gcc-trunk/gcc/c/c-parser.cc:1695
> 0xdc68d3 c_parse_file()
> /repo/gcc-trunk/gcc/c/c-parser.cc:24213
> 0xe28a61 c_common_parse_file()
> /repo/gcc-trunk/gcc/c-family/c-opts.cc:1247
> Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
> Please include the complete backtrace with any bug report.
> See <https://gcc.gnu.org/bugs/> for instructions.
My apologies, the above belongs to PR107261
prev parent reply other threads:[~2022-10-19 14:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 9:45 [Bug target/62133] New: " sampath.pamidi at gmail dot com
2021-08-09 6:50 ` [Bug target/62133] " pinskia at gcc dot gnu.org
2022-10-19 14:30 ` zsojka at seznam dot cz
2022-10-19 14:34 ` zsojka at seznam dot cz [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-62133-4-FINOjPVUK9@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).